From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] First round of SCSI updates for 2.6.39 merge window
Date: Thu, 28 Jul 2011 12:49:39 +0400 [thread overview]
Message-ID: <1311842979.30253.29.camel@mulgrave> (raw)
In-Reply-To: <20110723102719.a7f26008.rdunlap@xenotime.net>
On Sat, 2011-07-23 at 10:27 -0700, Randy Dunlap wrote:
> On Sat, 23 Jul 2011 21:17:32 +0400 James Bottomley wrote:
>
> > This represents the usual round of driver updates (fcoe, bfa, mpt2sas,
> > iscsi, bnx2fc) plus a couple of fixes that didn't make 3.0 including the
> > USB force eject oops.
> >
> > The patch is available here:
> >
> > master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
>
> Hi James,
>
> (please fix $subject)
Hmm, reusability gone too far
> What has happened to these 2 patches from 2011-June-21 ?
>
> Subject: [PATCH] scsi: fix NCR_Q720 section mismatch warning
> Subject: [PATCH] scsi: fix sim710 section mismatch warnings
Ralf is reworking them. Basically there's no point mucking with
creating work via the endless sectional annotators in obsolete drivers,
so he was just going to strip the annotations where they cause problems.
James
next prev parent reply other threads:[~2011-07-28 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 17:17 [GIT PULL] First round of SCSI updates for 2.6.39 merge window James Bottomley
2011-07-23 17:27 ` Randy Dunlap
2011-07-28 8:49 ` James Bottomley [this message]
2011-07-28 15:55 ` Randy Dunlap
2011-07-23 21:49 ` Giridhar Malavali
-- strict thread matches above, loose matches on Subject: below --
2011-05-20 10:41 James Bottomley
2011-05-20 13:01 ` Christoph Hellwig
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=1311842979.30253.29.camel@mulgrave \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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