On Thu, Oct 31, 2019 at 10:12:04AM -0600, Simon Glass wrote:
Hi Tom,
On Thu, 31 Oct 2019 at 09:50, Tom Rini trini@konsulko.com wrote:
On Thu, Oct 31, 2019 at 09:19:50AM -0600, Simon Glass wrote:
Hi Tom,
On Thu, 31 Oct 2019 at 07:55, Tom Rini trini@konsulko.com wrote:
On Thu, Oct 31, 2019 at 07:43:05AM -0600, Simon Glass wrote:
Update this tool to use Python 3 to meet the 2020 deadline.
Unfortunately this introduces a test failure due to a problem in pylibfdt on Python 3. I will investigate.
Signed-off-by: Simon Glass sjg@chromium.org
Changes in v2:
- Add a few more patches to correct remaining problems
Is there still a failure or did you fix it? If there still is, what board(s) make use of that feature? Thanks!
Everything works fine now, so far as I can tell. The pylibfdt fix was accepted upstream, too.
OK, so a v3 to fix the commit message :) Do you want to pull all of this together in the end and give me a PR or do you want me to (and kick Azure/Travis/GitLab as needed) ?
Ooops, OK, will do.
I am happy to do either. I got a successful run. The latest one is going here, but only has commit-message changes:
https://gitlab.denx.de/u-boot/custodians/u-boot-dm/pipelines/1181
OK. Can you please put together a fdt PR with those changes and then I'll grab all of the rest of the Python stuff and make sure all the CIs pass? Thanks again!