From: Greg KH <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: Kay Sievers <kay@vrfy.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] driver core patches for 3.5-rc1 - try 2
Date: Tue, 22 May 2012 23:12:16 -0700 [thread overview]
Message-ID: <20120523061216.GA19584@kroah.com> (raw)
In-Reply-To: <1337724736.11918.8.camel@joe2Laptop>
On Tue, May 22, 2012 at 03:12:16PM -0700, Joe Perches wrote:
> On Tue, 2012-05-22 at 15:05 -0700, Greg KH wrote:
> > On Tue, May 22, 2012 at 02:58:47PM -0700, Joe Perches wrote:
> > > How is it really better that what is available now?
> > >
> > > Perhaps it would be better to respin all the
> > > printk modifications without adding [v]printk_emit
> > > and have the [v]printk_emit bits debated a bit more.
> >
> > I'm always glad to review patches, but to just propose something that
> > works to be reverted without a patch to replace the functionality, isn't
> > ok.
>
> It hasn't been committed yet in anything other than
> -next.
>
> Lots of stuff gets committed there and later removed
> and hits Linus' mainline tree.
Sorry, but as people are "downstream" for me, I do not rebase my trees,
unless something really bad happened (i.e. I messed up the tree). So
this will not happen, sorry.
Also, the patches are all in Linus's tree now, so the point is moot.
thanks,
greg k-h
next prev parent reply other threads:[~2012-05-23 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1337723927.9270.15.camel@joe2Laptop>
2012-05-22 22:08 ` [GIT PATCH] driver core patches for 3.5-rc1 - try 2 Greg KH
[not found] ` <20120522220534.GC12705@kroah.com>
2012-05-22 22:12 ` Joe Perches
2012-05-23 6:12 ` Greg KH [this message]
2012-05-22 22:01 Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2012-05-22 15:14 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=20120523061216.GA19584@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--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.