From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] scsi fixes for 3.0-rc5
Date: Thu, 7 Jul 2011 14:12:58 -0700 [thread overview]
Message-ID: <20110707141258.786bb7f9.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110704165535.ce364909.randy.dunlap@oracle.com>
On Mon, 4 Jul 2011 16:55:35 -0700 Randy Dunlap wrote:
> On Mon, 04 Jul 2011 16:00:16 -0500 James Bottomley wrote:
>
> > This is a couple of driver fixes and the addition of the isci intel SAS
> > driver under the new driver merge exception. The isci tree is cleanly
> > separated with everything under drivers/scsi/isci (plus the
> > Makefile/Kconfig plumbing and one firmware file under firmware/isci).
> > The driver itself weighs in at around 23k lines, which is on the heavy
> > side, but Christoph Hellwig and I think it's ready enough to accept now
> > so that we have a working driver by the time the motherboards ship
> > (estimated to be in the 3.0 release timeframe).
> >
> > The patch is available here:
> >
> > master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
> >
> > The shortlog for just the driver fixes (lest they get lost in the flood) is:
> >
> > Brian King (1):
> > ibmvfc: Fix Virtual I/O failover hang
> >
> > Stephen M. Cameron (2):
> > hpsa: fix potential overrun while memcpy'ing sense data
> > hpsa: fix dma unmap error in hpsa_passthru_ioctl
>
> Hi James,
>
> Did you do anything with these 2 scsi section mismatch patches from June 21?
> I don't see them in any of your scsi git trees, although I could have
> missed them.
>
> Subject: [PATCH] scsi: fix NCR_Q720 section mismatch warning
> http://marc.info/?l=linux-scsi&m=130868730409600&w=2
>
> Subject: [PATCH] scsi: fix sim710 section mismatch warnings
> http://marc.info/?l=linux-scsi&m=130868736409676&w=2
p i n g
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-07-07 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 21:00 [GIT PULL] scsi fixes for 3.0-rc5 James Bottomley
2011-07-04 23:55 ` Randy Dunlap
2011-07-07 21:12 ` Randy Dunlap [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=20110707141258.786bb7f9.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox