mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: David Jander <david@protonic.nl>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
	Barebox List <barebox@lists.infradead.org>,
	Marco Franchi <marco.franchi@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>
Subject: Re: Device-tree node renames break barebox/kernel compatibility...
Date: Wed, 13 Jun 2018 13:57:03 -0300	[thread overview]
Message-ID: <CAOMZO5Bp=j4GH+1cco8-iC+4p04Ommb+FjWFeE5_1vRUnHEwnw@mail.gmail.com> (raw)
In-Reply-To: <20180613085034.3d7ac581@erd980>

Hi David,

On Wed, Jun 13, 2018 at 3:50 AM, David Jander <david@protonic.nl> wrote:
o, it's not just you. Me and other people are with you.
>>
>> When talking about device tree stability we usually only talk about the
>> bindings, not about the structure of the trees. The problem here was
>> probably that people weren't aware that this change breaks stuff.
>
> That's exactly what I also thought. That's in part also why I sent this e-mail
> (the committers are in CC and hopefully listening ;-)
> Sorry for the spam in that regard.

I was not aware that removing the leading zeroes would cause any problem, sorry.

Maybe you could also report this problem to Rob Herring and the
devicetree mainling list.

Thanks

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2018-06-13 16:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 12:23 David Jander
2018-06-12 12:47 ` Sascha Hauer
2018-06-12 13:46   ` David Jander
2018-06-13  6:42     ` Sascha Hauer
2018-06-13  6:50       ` David Jander
2018-06-13 16:57         ` Fabio Estevam [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOMZO5Bp=j4GH+1cco8-iC+4p04Ommb+FjWFeE5_1vRUnHEwnw@mail.gmail.com' \
    --to=festevam@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=david@protonic.nl \
    --cc=fabio.estevam@nxp.com \
    --cc=marco.franchi@nxp.com \
    --cc=shawnguo@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox