From: "Love, Robert W" <robert.w.love@intel.com>
To: James Bottomley <james.bottomley@hansenpartnership.com>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Neil Horman <nhorman@redhat.com>,
"Fastabend, John R" <john.r.fastabend@intel.com>,
"fcoe-devel@open-fcoe.org" <fcoe-devel@open-fcoe.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: fcoe pull request for 3.9-rc
Date: Thu, 27 Jun 2013 15:39:30 +0000 [thread overview]
Message-ID: <51CC5CB2.80108@intel.com> (raw)
In-Reply-To: <1372313642.557.19.camel@dabdike>
On Wed 26 Jun 2013 11:14:02 PM PDT, James Bottomley wrote:
> On Tue, 2013-06-25 at 20:55 +0000, Love, Robert W wrote:
>> The following changes since commit 1e876e3b1a9df25bb04682b0d48aaa7e8ae1fc82:
>>
>> Merge branch 'for-linus' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux (2013-06-25
>> 09:08:07 -1000)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/rwlove/fcoe.git
>> tags/critical_fix_for_3.9
>
> This is simple and I can review from the attached patch, so I'll take it
> this time. But, please, next time follow proper process. That means the
> individual patches should go over the SCSI mailing list for review
> *before* they're sent in a pull request.
>
The reason I sent this pull request directly to Linus was that the
patches I mailed at (2013-05-21) RC2 had not yet seen any attention
since they were posted to linux-scsi. It is now RC7 and with 5 weeks of
inactivity on my initial 3.10 patch series I had no faith that this
critical fix would make it through the SCSI tree before the 3.10 kernel
was released. FYI, Linus has taken this change already.
I would have preferred to send the patch to linux-scsi for review
first, but it had been thoroughly reviewed on the FCoE list, it's a
fairly trivial change and I was a hurry to get it into Linus' inbox
given his statement about "finding new ways to insult your pets." The
patch is also part of the pull request, so it was review-able by anyone
on linux-scsi or linux-kernel.
Thanks, //Rob
PS: I totally botched the title of this pull request, obviously it
should say "fcoe pull request for 3.10-rc".
prev parent reply other threads:[~2013-06-27 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 20:55 fcoe pull request for 3.9-rc Love, Robert W
2013-06-27 6:14 ` James Bottomley
2013-06-27 15:39 ` Love, Robert W [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=51CC5CB2.80108@intel.com \
--to=robert.w.love@intel.com \
--cc=fcoe-devel@open-fcoe.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=john.r.fastabend@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nhorman@redhat.com \
--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).