All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Introduce builtin_platform_driver for non modules
Date: Wed, 1 Jul 2015 08:29:17 -0700	[thread overview]
Message-ID: <20150701152917.GA27435@kroah.com> (raw)
In-Reply-To: <20150701165355.43e4cbbc@canb.auug.org.au>

On Wed, Jul 01, 2015 at 04:53:55PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Tue, 30 Jun 2015 18:24:58 -0700 Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > > The following changes since commit 0f57d86787d8b1076ea8f9cbdddda2a46d534a27:
> > > 
> > >   Linux 4.1-rc8 (2015-06-14 15:51:10 -1000)
> > > 
> > > are available in the git repository at:
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git tags/module-builtin_driver-v4.1-rc8
> > > 
> > > for you to fetch changes up to 77459a0feca4ae8757a905fd1791f039479e8e1e:
> > > 
> > >   drivers/clk: convert sunxi/clk-mod0.c to use builtin_platform_driver (2015-06-16 14:12:39 -0400)
> > 
> > Was this ever in linux-next?
> 
> Yes, since next-20150617.

Ah good, missed that, sorry.

> >  Ideally some subsystem people would ack it...
> 
> Most of the patches have at least one Ack

Ok, I was looking at the one that touched the driver core :)

Anyway, this is fine with me, sorry for the noise.

greg k-h

  reply	other threads:[~2015-07-01 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01  1:19 [GIT PULL] Introduce builtin_platform_driver for non modules Paul Gortmaker
2015-07-01  1:24 ` Greg KH
2015-07-01  6:53   ` Stephen Rothwell
2015-07-01 15:29     ` Greg KH [this message]
2015-07-01 15:33   ` Paul Gortmaker
2015-07-01 15:39     ` Greg KH

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=20150701152917.GA27435@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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 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.