From: Simon Horman <horms@verge.net.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
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: Sat, 8 Apr 2017 16:08:48 -0400 [thread overview]
Message-ID: <20170408200848.GC6533@verge.net.au> (raw)
In-Reply-To: <20170408153505.GA1140@kroah.com>
On Sat, Apr 08, 2017 at 05:35:05PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Apr 03, 2017 at 06:28:31AM -0400, Simon Horman wrote:
> > 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.
>
> Pull it into where? Why do I need this if they are going in through
> your tree?
Good point. I don't think you need to pull it unless it would satisfy
dependencies you have and it seems there are none at this time.
prev parent reply other threads:[~2017-04-08 20:08 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
2017-04-08 15:35 ` Greg Kroah-Hartman
2017-04-08 20:08 ` 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=20170408200848.GC6533@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