public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Peer Chen <peerchen@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-ide <linux-ide@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>, Kuan Luo <kluo@nvidia.com>
Subject: Re: [PATCH] sata_nv,ahci: add the ahci legacy mode support to sata_nv
Date: Fri, 12 Oct 2007 17:17:47 -0400	[thread overview]
Message-ID: <470FE47B.5060505@garzik.org> (raw)
In-Reply-To: <200709251323031982245@gmail.com>

Peer Chen wrote:
> Add the ahci controller legacy mode support to sata_nv.
> Move the DIDs of legacy mode from ahci.c to sata_nv.c
> 
> The patch base on kernel 2.6.23-rc8
> 
> Signed-off-by: Peer Chen <peerchen@gmail.com>

Would you mind checking libata-dev.git#upstream, and make sure it has 
all the NV patches?

I'm thinking I should go ahead and push the 'nv-swncq' branch, which 
contains the sata_nv updates for swncq.  They have been in -mm for a 
while.  I am leaning towards leaving the default to 'off' for 2.6.24 though.

Comments welcome...

	Jeff




  parent reply	other threads:[~2007-10-12 21:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25  5:23 [PATCH] sata_nv,ahci: add the ahci legacy mode support to sata_nv Peer Chen
2007-09-25  7:08 ` Jeff Garzik
2007-09-25  7:52   ` Peer Chen
2007-09-25  8:13     ` Jeff Garzik
2007-09-25  9:08       ` Peer Chen
2007-10-12 21:17 ` Jeff Garzik [this message]
2007-10-16  8:08   ` peer chen
2007-10-19  2:56     ` Jeff Garzik
2007-10-19  6:58       ` peer chen
2007-10-19  7:25         ` Jeff Garzik
2007-10-22  1:55           ` peer chen
2007-11-10  4:04             ` Jeff Garzik
2007-11-10  5:00               ` Jeff Garzik
2007-11-10 19:00                 ` Robert Hancock
2007-12-11 12:04                   ` [PATCH] sata_nv,adma: fix error when rmmod sata_nv Kuan Luo
2007-12-12  8:18                     ` Tejun Heo
2007-12-13  3:10                       ` Kuan Luo

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=470FE47B.5060505@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=kluo@nvidia.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peerchen@gmail.com \
    /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