From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
Inaky Perez-Gonzalez <inaky@linux.intel.com>,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: driver-core.current tree build failure
Date: Thu, 22 Jan 2009 08:08:50 -0800 [thread overview]
Message-ID: <20090122160850.GC9047@kroah.com> (raw)
In-Reply-To: <20090122173901.1828a3a4.sfr@canb.auug.org.au>
On Thu, Jan 22, 2009 at 05:39:01PM +1100, Stephen Rothwell wrote:
> This has been submitted to Linus stating that it has been in at least one
> linux-next tree. It has *not* been in linux-next until today (you do
> neither of us a favour by claiming otherwise) and I am reverting it from
> there.
My apologies, I thought it had been in one linux-next by virtue of when
I had checked it into my tree.
I'll go fix this up and kick Inaky the next time I see him for sending
me a untested patch :)
thanks,
greg k-h
prev parent reply other threads:[~2009-01-22 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 6:39 linux-next: driver-core.current tree build failure Stephen Rothwell
2009-01-22 16:08 ` Greg KH [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=20090122160850.GC9047@kroah.com \
--to=greg@kroah.com \
--cc=inaky@linux.intel.com \
--cc=linux-next@vger.kernel.org \
--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 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).