public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>,
	Olof Johansson <olof@lixom.net>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [git pull] base: soc: Improvements for the SoC bus and soc_device_match()
Date: Mon, 3 Apr 2017 06:28:31 -0400	[thread overview]
Message-ID: <20170403102831.GF31988@verge.net.au> (raw)
In-Reply-To: <1490950460-8945-1-git-send-email-geert+renesas@glider.be>

On Fri, Mar 31, 2017 at 10:54:20AM +0200, Geert Uytterhoeven wrote:
> 	Hi Greg,
> 	Hi Arnd, Kevin, Olof,
> 	Hi Magnus, Simon,
> 
> The following changes since commit c470abd4fde40ea6a0846a2beab642a578c0b8cd:
> 
>   Linux 4.10 (2017-02-19 14:34:00 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git tags/soc-device-match-tag2
> 
> for you to fetch changes up to 6e12db376b60b7158e4e6006af60566f8c68f7ab:
> 
>   base: soc: Allow early registration of a single SoC device (2017-03-29 21:43:26 +0200)

Hi Geert,

I have pulled this into the renesas tree.

Hi Greg,

I would be most grateful if you could pull the above tag too.

> ----------------------------------------------------------------
> base: soc: Improvements for the SoC bus and soc_device_match()
> 
> This 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().
> 
> Hence this will serve as an immutable branch between the driver core,
> arm-soc, and renesas trees, to allow queueing the Renesas R-Car SYSC
> changes on top in the renesas tree.
> 
> All changes in this pull request have been Acked by Arnd.
> 
> Thanks for pulling!
> ----------------------------------------------------------------
> Geert Uytterhoeven (2):
>       base: soc: Let soc_device_match() return no match when called too early
>       base: soc: Allow early registration of a single SoC device
> 
>  drivers/base/soc.c | 52 ++++++++++++++++++++++++++++++++++------------------
>  1 file changed, 34 insertions(+), 18 deletions(-)
> 
> Gr{oetje,eeting}s,
> 
> 						Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> 							    -- Linus Torvalds
> 

  reply	other threads:[~2017-04-03 10:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31  8:54 [git pull] base: soc: Improvements for the SoC bus and soc_device_match() Geert Uytterhoeven
2017-04-03 10:28 ` Simon Horman [this message]
2017-04-08 15:35   ` Greg Kroah-Hartman
2017-04-08 20:08     ` Simon Horman

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=20170403102831.GF31988@verge.net.au \
    --to=horms@verge.net.au \
    --cc=arnd@arndb.de \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox