All of lore.kernel.org
 help / color / mirror / Atom feed
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 16:31:07 -0400	[thread overview]
Message-ID: <40B6500B.5000009@pobox.com> (raw)
In-Reply-To: <C064BF1617D93B4B83714E38C4653A6E0AF48249@mail-sc-10.nvidia.com>

Brian Lazara wrote:
> We do plan on moving our SATA support to libata.

cool


> Patches for 2.4.27-pre2 and 2.6.6 to add device IDs for new nForce IDE
> and SATA controllers. Rename some of the existing controller names to
> correctly match released product names. 

The patch looks OK to me, though the final call is up to Bart.

FWIW, when you included the patch inline, your email editor word-wrapped 
it so it will not apply.

If Microsoft Outlook (or whatever) cannot produce decent patches, you 
may need to include your patches _twice_ -- once in plaintext (with 
annoying word wrap) for review, and once as you did initially, as a 
base64 attachment.

Most MUA's are able to attach patches as plaintext (not base64), so see 
if there are setting you can flip...

	Jeff



  reply	other threads:[~2004-05-27 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 20:21 [PATCH] add new nForce IDE/SATA device IDs Brian Lazara
2004-05-27 20:21 ` Brian Lazara
2004-05-27 20:31 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-27 18:24 Brian Lazara
2004-05-27 19:38 ` 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=40B6500B.5000009@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.