linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] base: soc: soc_device_match() improvements
Date: Fri, 31 Mar 2017 10:39:37 +0200	[thread overview]
Message-ID: <20170331083934.GA14676@verge.net.au> (raw)
In-Reply-To: <CAK8P3a168j6BYzWkDzHDp0tBwiOj=JP-G2LXUiLiDFphbV5vdg@mail.gmail.com>

On Wed, Mar 29, 2017 at 09:48:48PM +0200, Arnd Bergmann wrote:
> On Wed, Mar 29, 2017 at 9:38 PM, Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
> >         Hi Arnd, Greg, Kevin, Magnus, Olof, Simon,
> >
> > This patch series contains two improvements for the SoC bus and
> > soc_device_match().  The second one is a dependency for handling
> > different SoC revisions in the Renesas R-Car SYSC driver, which manages
> > PM Domains and thus needs to be initialized from an early_initcall[*].
> >
> > Changes compared to v1:
> >   - Drop RFC state,
> >   - Add more explanation,
> >   - Add Acked-by.
> >
> > Due to the dependency, and as changes for the Renesas R-Car SYSC driver
> > typically go in through the renesas and arm-soc trees, and if you agree,
> > I would like to send a pull request for these changes, to be pulled by
> > all of the driver core, renesas, and arm-soc trees.  This is similar to
> > how soc_device_match() was integrated earlier.
> > Then the Renesas R-Car SYSC driver changes can easily be queued on top
> > in the renesas tree afterwards.
> >
> > Do you agree?
> > Thanks for your answer!
> 
> Merging this through arm-soc is fine with me.

Thanks, in that case I am fine with this plan.

> > P.S. If you think it's already too late in the cycle to queue Renesas
> > R-Car SYSC driver changes for v4.12 on top, please say so.  Then the
> > dependency is relaxed, and this series can just go in through the
> > driver core tree, with the Renesas part to follow for v4.13.
> 
> We can take it for 4.12.

Thanks again. My preference at this time is to deffer the DT changes to v4.13
as it seems somewhat simpler and I'm not aware of any urgency to get them
into v4.12.

      reply	other threads:[~2017-03-31  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 19:38 [PATCH v2 0/2] base: soc: soc_device_match() improvements Geert Uytterhoeven
2017-03-29 19:38 ` [PATCH v2 1/2] base: soc: Let soc_device_match() return no match when called too early Geert Uytterhoeven
2017-03-29 19:38 ` [PATCH v2 2/2] base: soc: Allow early registration of a single SoC device Geert Uytterhoeven
2017-03-29 19:48 ` [PATCH v2 0/2] base: soc: soc_device_match() improvements Arnd Bergmann
2017-03-31  8:39   ` Simon Horman [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=20170331083934.GA14676@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).