From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Peer Chen <pchen@nvidia.com>,
Christoph Hellwig <hch@infradead.org>,
Prakash Punnoor <prakash@punnoor.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Kuan Luo <kluo@nvidia.com>
Subject: Re: [PATCH] SCSI: Add the SGPIO support for sata_nv.c
Date: Wed, 31 Jan 2007 15:21:36 -0800 [thread overview]
Message-ID: <20070131152136.7d0a05ff.kristen.c.accardi@intel.com> (raw)
In-Reply-To: <455DF9AE.3000406@garzik.org>
On Fri, 17 Nov 2006 13:04:30 -0500
Jeff Garzik <jeff@garzik.org> wrote:
> Peer Chen wrote:
> > I didn't get any comment from you guys for new patch, does someone take
> > care this patch, do we still need some modification upon it? Or do we
> > need re-submit it in other thread?
>
> For my part, it's in my queue of things to review. I need to figure out
> the best way to export this support.
>
> Jeff
Adding SGPIO support directly into an individual SATA driver seems to be
a very bad idea since SGPIO is a) a protocol that can be used by many
different SATA controllers and is not nvidia specific and b) can also
be used by SAS.
next prev parent reply other threads:[~2007-01-31 23:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 8:36 Peer Chen
2006-11-17 15:06 ` Heikki Orsila
2006-11-17 18:04 ` Jeff Garzik
2006-11-20 2:20 ` Peer Chen
2007-01-31 23:21 ` Kristen Carlson Accardi [this message]
2007-02-01 19:55 ` Andy Currid
2007-02-01 21:49 ` Kristen Carlson Accardi
[not found] <45A377D2.60401@garzik.org>
2007-01-10 2:50 ` Robert Hancock
[not found] <15F501D1A78BD343BE8F4D8DB854566B059FE0B3@hkemmail01.nvidia.com>
2006-10-31 8:43 ` Peer Chen
2006-10-31 10:40 ` Christoph Hellwig
2006-10-31 12:37 ` Prakash Punnoor
2006-11-07 9:55 ` Peer Chen
2007-11-07 4:09 ` Yinghai Lu
2009-01-18 9:20 ` Yinghai Lu
2006-11-01 1:39 ` Jeff Garzik
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=20070131152136.7d0a05ff.kristen.c.accardi@intel.com \
--to=kristen.c.accardi@intel.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=kluo@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pchen@nvidia.com \
--cc=prakash@punnoor.de \
/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
Powered by JetHome