All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Olof Johansson <olof@lixom.net>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Arnd Bergmann <arnd@arndb.de>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Emilio Lopez <emilio@elopez.com.ar>
Subject: Re: [PATCH 0/2] ARM: sunxi: Convert DTSI to new CPU bindings
Date: Sat, 29 Jun 2013 21:11:32 +0100	[thread overview]
Message-ID: <20130629201132.GA9375@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <20130629193819.GD3353@n2100.arm.linux.org.uk>

On Sat, Jun 29, 2013 at 08:38:19PM +0100, Russell King - ARM Linux wrote:
> On Fri, Jun 28, 2013 at 01:05:42PM -0700, Olof Johansson wrote:
> > On Fri, Jun 28, 2013 at 1:03 PM, Maxime Ripard
> > <maxime.ripard@free-electrons.com> wrote:
> > > On Fri, Jun 28, 2013 at 06:15:32PM +0100, Lorenzo Pieralisi wrote:
> > >> The patch above should already be queued in next/dt right ?
> > >
> > > Indeed.
> > >
> > > Then why the latest patch of your patchset got in 3.10, while the
> > > patches actually fixing the DT it would have impacted were delayed to
> > > 3.11?
> > >
> > > (And why was it merged so late in the development cycle?)
> > 
> > This. So now we have to scramble because some device trees will
> > produce warnings at boot.
> > 
> > Russell, the alternative is to revert Lorenzo's patch for 3.10 (and
> > re-introduce it for 3.11). Do you have a preference?
> 
> Sorry but I really don't understand what all the fuss in this thread
> is about.
> 
> This thread seems to be saying that two development patches were
> merged, which were 7762/1 and 7763/1, and that 7764/1 is a fix?
> Are you sure about that, because that's not how they're described,
> and not how they look either.

Russell, technically speaking what are you saying is correct, but the
problem is that the 7762/1, 7763/1 and 7764/1 were part of a series
to update DT cpu/cpus bindings, topology, bring dts files up to standard
and update kernel code to comply. The problem is the following: if
7762/1 is merged but dts updates in the arm-soc tree (that can be
considered fixes, but as I said it is hard to draw a line between fixes
and dev since this series is meant to redefine the DT bindings themselves
to make them as compliant as possible with ePAPR) are not merged at the same
time, the kernel triggers warnings for boards with non-compliant dts.

That's the same reason why I asked to drop 7762/1 from stable queues,
since if it gets there all dts updates should get there at the same
time.

Please let me know if that's unclear and how I can help you fix the
problem, I am just trying to syncronize all the changes the best I can.

Apologies and thanks,
Lorenzo


WARNING: multiple messages have this Message-ID (diff)
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: sunxi: Convert DTSI to new CPU bindings
Date: Sat, 29 Jun 2013 21:11:32 +0100	[thread overview]
Message-ID: <20130629201132.GA9375@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <20130629193819.GD3353@n2100.arm.linux.org.uk>

On Sat, Jun 29, 2013 at 08:38:19PM +0100, Russell King - ARM Linux wrote:
> On Fri, Jun 28, 2013 at 01:05:42PM -0700, Olof Johansson wrote:
> > On Fri, Jun 28, 2013 at 1:03 PM, Maxime Ripard
> > <maxime.ripard@free-electrons.com> wrote:
> > > On Fri, Jun 28, 2013 at 06:15:32PM +0100, Lorenzo Pieralisi wrote:
> > >> The patch above should already be queued in next/dt right ?
> > >
> > > Indeed.
> > >
> > > Then why the latest patch of your patchset got in 3.10, while the
> > > patches actually fixing the DT it would have impacted were delayed to
> > > 3.11?
> > >
> > > (And why was it merged so late in the development cycle?)
> > 
> > This. So now we have to scramble because some device trees will
> > produce warnings at boot.
> > 
> > Russell, the alternative is to revert Lorenzo's patch for 3.10 (and
> > re-introduce it for 3.11). Do you have a preference?
> 
> Sorry but I really don't understand what all the fuss in this thread
> is about.
> 
> This thread seems to be saying that two development patches were
> merged, which were 7762/1 and 7763/1, and that 7764/1 is a fix?
> Are you sure about that, because that's not how they're described,
> and not how they look either.

Russell, technically speaking what are you saying is correct, but the
problem is that the 7762/1, 7763/1 and 7764/1 were part of a series
to update DT cpu/cpus bindings, topology, bring dts files up to standard
and update kernel code to comply. The problem is the following: if
7762/1 is merged but dts updates in the arm-soc tree (that can be
considered fixes, but as I said it is hard to draw a line between fixes
and dev since this series is meant to redefine the DT bindings themselves
to make them as compliant as possible with ePAPR) are not merged at the same
time, the kernel triggers warnings for boards with non-compliant dts.

That's the same reason why I asked to drop 7762/1 from stable queues,
since if it gets there all dts updates should get there at the same
time.

Please let me know if that's unclear and how I can help you fix the
problem, I am just trying to syncronize all the changes the best I can.

Apologies and thanks,
Lorenzo

  reply	other threads:[~2013-06-29 20:11 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 16:44 [PATCH 0/2] ARM: sunxi: Convert DTSI to new CPU bindings Maxime Ripard
2013-06-28 16:44 ` Maxime Ripard
2013-06-28 16:44 ` [PATCH 1/2] ARM: dts: sunxi: cpus/cpu nodes dts updates Maxime Ripard
2013-06-28 16:44   ` Maxime Ripard
2013-06-28 16:44 ` [PATCH 2/2] sunxi: a10s: dtsi: Convert cpu node to the new cpu bindings Maxime Ripard
2013-06-28 16:44   ` Maxime Ripard
2013-06-28 17:15 ` [PATCH 0/2] ARM: sunxi: Convert DTSI to new CPU bindings Lorenzo Pieralisi
2013-06-28 17:15   ` Lorenzo Pieralisi
2013-06-28 20:03   ` Maxime Ripard
2013-06-28 20:03     ` Maxime Ripard
2013-06-28 20:05     ` Olof Johansson
2013-06-28 20:05       ` Olof Johansson
2013-06-28 21:45       ` Lorenzo Pieralisi
2013-06-28 21:45         ` Lorenzo Pieralisi
2013-06-29 18:07         ` Maxime Ripard
2013-06-29 18:07           ` Maxime Ripard
2013-06-29 19:03           ` Lorenzo Pieralisi
2013-06-29 19:03             ` Lorenzo Pieralisi
2013-06-29 19:38       ` Russell King - ARM Linux
2013-06-29 19:38         ` Russell King - ARM Linux
2013-06-29 20:11         ` Lorenzo Pieralisi [this message]
2013-06-29 20:11           ` Lorenzo Pieralisi
2013-06-29 22:54         ` Olof Johansson
2013-06-29 22:54           ` Olof Johansson
2013-06-29 23:14           ` Russell King - ARM Linux
2013-06-29 23:14             ` Russell King - ARM Linux
2013-06-29 23:20             ` Olof Johansson
2013-06-29 23:20               ` Olof Johansson
2013-06-30  9:48         ` Lorenzo Pieralisi
2013-06-30  9:48           ` Lorenzo Pieralisi
2013-07-05 10:19           ` Lorenzo Pieralisi
2013-07-05 10:19             ` Lorenzo Pieralisi
2013-07-05 10:19             ` Lorenzo Pieralisi
2013-07-12  9:37             ` Maxime Ripard
2013-07-12  9:37               ` Maxime Ripard
2013-07-12  9:37               ` Maxime Ripard
2013-07-02 12:12 ` Nicolas Ferre
2013-07-02 12:12   ` Nicolas Ferre
2013-07-02 12:56   ` Lorenzo Pieralisi
2013-07-02 12:56     ` Lorenzo Pieralisi

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=20130629201132.GA9375@e102568-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=arnd@arndb.de \
    --cc=emilio@elopez.com.ar \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=maxime.ripard@free-electrons.com \
    --cc=olof@lixom.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.