From: Jeff Garzik <jgarzik@pobox.com>
To: Brian Lazara <blazara@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: [PATCH] add new nForce IDE/SATA device IDs
Date: Thu, 27 May 2004 15:38:00 -0400 [thread overview]
Message-ID: <40B64398.7090808@pobox.com> (raw)
In-Reply-To: <C064BF1617D93B4B83714E38C4653A6E0AF48248@mail-sc-10.nvidia.com>
Brian Lazara wrote:
> Patches to add device IDs for new nForce IDE and SATA controllers.
> Rename some of the existing controller names to correctly match released
> product names.
>
> Patches against 2.4.27-pre2 and 2.6.6
It is difficult to review patches that look like the following...
please include the patches include, or attach them as plaintext.
Three other comments:
1) please CC linux-ide@vger.kernel.org on all IDE/SATA-related patches
2) Please To: or CC: Bartlomiej (cc'd on this email) on all drivers/ide
patches, as he is the IDE maintainer.
3) Normally we want to add SATA support to libata not drivers/ide. Do
the nVidia SATA chips support SATA SCRs or anything like that? Why not
use libata?
Content-Type: application/octet-stream;
name="linux-2.4.27-pre2-nforce-ck804-ide.patch"
Content-Transfer-Encoding: base64
Content-Description: linux-2.4.27-pre2-nforce-ck804-ide.patch
Content-Disposition: attachment;
filename="linux-2.4.27-pre2-nforce-ck804-ide.patch"
ZGlmZiAtdXByTiAtWCBkb250ZGlmZiBsaW51eC0yLjQuMjctcHJlMi9kcml2ZXJzL2lkZS9wY2kv
YW1kNzR4eC5jIGxpbnV4LTIuNC4yNy1wcmUyLW5mb3JjZS1jazgwNC1pZGUvZHJpdmVycy9pZGUv
cGNpL2FtZDc0eHguYwotLS0gbGludXgtMi40LjI3LXByZTIvZHJpdmVycy9pZGUvcGNpL2FtZDc0
eHguYwkyMDA0LTA0LTE0IDA2OjA1OjI5LjAwMDAwMDAwMCAtMDcwMAorKysgbGludXgtMi40LjI3
LXByZTItbmZvcmNlLWNrODA0LWlkZS9kcml2ZXJzL2lkZS9wY2kvYW1kNzR4eC5jCTIwMDQtMDUt
MTcgMTM6Mjc6MzEuMDAwMDAwMDAwIC0wNzAwCkBAIC0xLDcgKzEsOCBAQAogLyoKICAqIFZlcnNp
b24gMi4xMwogICoKLSAqIEFNRCA3NTUvNzU2Lzc2Ni84MTExIGFuZCBuVmlkaWEgbkZvcmNlLzIv
MnMvMy8zcyBJREUgZHJpdmVyIGZvciBMaW51eC4KKyAqIEFNRCA3NTUvNzU2Lzc2Ni84MTExIGFu
ZCBuVmlkaWEgbkZvcmNlLzIvMnMvMy8zcy9DSzgwNC9NQ1AwNCAKKyAqIElERSBkcml2ZXIgZm9y
next prev parent reply other threads:[~2004-05-27 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 18:24 [PATCH] add new nForce IDE/SATA device IDs Brian Lazara
2004-05-27 19:38 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-27 20:21 Brian Lazara
2004-05-27 20:31 ` 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=40B64398.7090808@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=blazara@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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