From: Greg KH <gregkh@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
linux-scsi@vger.kernel.org, jacek.danecki@intel.com,
ed.ciechanowski@intel.com, linux-kernel@vger.kernel.org,
dmilburn@redhat.com, edmund.nadolski@intel.com,
Jeff Garzik <jeff@garzik.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] firmware/efi: export a routine to retrieve efi-variables by GUID
Date: Fri, 18 Mar 2011 17:22:46 -0700 [thread overview]
Message-ID: <20110319002246.GB14249@suse.de> (raw)
In-Reply-To: <AANLkTim+HB0GWzGiif=MvYHaiXMSLuVB6R0=UK3906xU@mail.gmail.com>
On Fri, Mar 18, 2011 at 04:10:10PM -0700, Dan Williams wrote:
> > I needed all patches in linux-next _before_ the merge window opened to
> > be able to accept it.
>
> Yes, I know, and as dmaengine maintainer I also hate being ambushed by
> last minute patches, but now I am unfortunately one of those annoying
> people on the other side of the coin.
Then you should know better than to try to go around the well-known
rules :)
> The review has been intermittent until very recently. Given that
> fact, James was understandably not ready to take it into
> drivers/scsi/. So the thought was to leave time for the review to pan
> out and then attempt a post -rc1 merge through scsi or staging.
There are no "post -rc1" merges for staging, it follows the same rules
as the rest of the kernel. Which means that you will have to wait for
.40 before it can be merged, sorry.
> > So, sorry, it will have to wait until .40.
> > Please send me the isci driver and I will be glad to queue it up for
> > staging for that kernel.
>
> We will submit a revised driver in the next few weeks.
Fine, I'll queue it up for .40 then.
greg k-h
next prev parent reply other threads:[~2011-03-19 0:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 22:16 [PATCH] firmware/efi: export a routine to retrieve efi-variables by GUID Dan Williams
2011-03-18 22:50 ` Greg KH
2011-03-18 23:10 ` Dan Williams
2011-03-18 23:10 ` Dan Williams
2011-03-19 0:22 ` Greg KH [this message]
2011-03-19 1:15 ` Dan Williams
2011-03-20 0:14 ` Greg KH
2011-03-20 1:13 ` James Bottomley
2011-03-21 19:07 ` Dan Williams
2011-03-21 19:12 ` Christoph Hellwig
2011-03-21 18:41 ` Dan Williams
2011-03-22 3:49 ` Matt Domsch
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=20110319002246.GB14249@suse.de \
--to=gregkh@suse.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmilburn@redhat.com \
--cc=ed.ciechanowski@intel.com \
--cc=edmund.nadolski@intel.com \
--cc=hch@infradead.org \
--cc=jacek.danecki@intel.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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.