public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: James Bottomley <JBottomley@parallels.com>,
	Christoph Hellwig <hch@lst.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Dave Jiang <dave.jiang@intel.com>,
	Jeff Skirvin <jeffrey.d.skirvin@intel.com>,
	Ed Ciechanowski <ed.ciechanowski@intel.com>,
	Ed Nadolski <edmund.nadolski@intel.com>,
	David Milburn <dmilburn@redhat.com>,
	Jeff Garzik <jeff@garzik.org>,
	Jacek Danecki <jacek.danecki@intel.com>,
	hare@suse.de
Subject: Re: [GIT PULL] isci: sas controller driver for 3.0
Date: Mon, 4 Jul 2011 15:45:29 +0200	[thread overview]
Message-ID: <20110704134529.GA8917@lst.de> (raw)
In-Reply-To: <1309563349.19567.26.camel@dwillia2-linux>

On Fri, Jul 01, 2011 at 04:35:48PM -0700, Dan Williams wrote:
> James, please pull from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/djbw/isci.git master
> 
> ...to receive the isci driver that supports the integrated 6Gb/s SAS
> capabilities of the upcoming Intel(R) C600 series chipset family.  This
> part is targeted at standard servers / workstations and provides
> up to 8-ports (2x4-port controllers) of SAS beyond the traditional SATA
> ports (surfaced by the ahci driver).

The driver looks okay to me.  It's not stellar, but so much better
than the original.  I'll make sure to keep your TODO list long after
the merge, though :)


  parent reply	other threads:[~2011-07-04 13:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 23:35 [GIT PULL] isci: sas controller driver for 3.0 Dan Williams
2011-07-02 22:45 ` James Bottomley
2011-07-03  2:43   ` Dan Williams
2011-07-03  5:16     ` James Bottomley
2011-07-03  5:46       ` Dan Williams
2011-07-03 11:37         ` Dan Williams
2011-07-03 19:14           ` James Bottomley
2011-07-04 13:45 ` Christoph Hellwig [this message]
2011-07-04 14:07   ` Douglas Gilbert
2011-07-04 14:38     ` Matthew Wilcox

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=20110704134529.GA8917@lst.de \
    --to=hch@lst.de \
    --cc=JBottomley@parallels.com \
    --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=hare@suse.de \
    --cc=jacek.danecki@intel.com \
    --cc=jeff@garzik.org \
    --cc=jeffrey.d.skirvin@intel.com \
    --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