From: Jeff Garzik <jeff@garzik.org>
To: "Gaston, Jason D" <jason.d.gaston@intel.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
htejun@gmail.com
Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ata_piix: IDE mode SATA patch for Intel Tolapai
Date: Fri, 07 Sep 2007 19:48:47 -0400 [thread overview]
Message-ID: <46E1E35F.1010907@garzik.org> (raw)
In-Reply-To: <39B20DF628532344BC7A2692CB6AEE0701BCF3BF@orsmsx420.amr.corp.intel.com>
Gaston, Jason D wrote:
>> -----Original Message-----
>> From: Jeff Garzik [mailto:jeff@garzik.org]
>> Sent: Friday, August 31, 2007 12:51 AM
>> To: Gaston, Jason D
>> Cc: linux-ide@vger.kernel.org; linux-kernel@vger.kernel.org;
>> htejun@gmail.com
>> Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ata_piix: IDE mode SATA patch
> for
>> Intel Tolapai
>>
>> Jason Gaston wrote:
>>> Resend trying to remove 8-bit characters in the email.
>>>
>>> This patch adds the Intel Tolapai IDE mode SATA controller DID's.
>>>
>>> Signed-off-by: Jason Gaston <jason.d.gaston@intel.com>
>> applied
>
> Jeff,
>
> I just noticed that the following section came through as spaces instead
> of tabs. Do I need to resend a corrected version?
>
> +static const struct piix_map_db tolapai_map_db = {
> + .mask = 0x3,
> + .port_enable = 0x3,
> + .map = {
> + /* PM PS SM SS MAP */
> + { P0, NA, P1, NA }, /* 00b */
> + { RV, RV, RV, RV }, /* 01b */
> + { RV, RV, RV, RV }, /* 10b */
> + { RV, RV, RV, RV },
> + },
> +};
that's always nice, yes :)
even better would be to run a script through #upstream, accomplishing
the same thing but for many drivers ;-)
prev parent reply other threads:[~2007-09-07 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 4:36 [PATCH 2.6.23-rc4][reRESEND] ata_piix: IDE mode SATA patch for Intel Tolapai Jason Gaston
2007-08-31 7:46 ` Jeff Garzik
2007-08-31 7:50 ` Jeff Garzik
2007-09-07 23:42 ` Gaston, Jason D
2007-09-07 23:42 ` Gaston, Jason D
2007-09-07 23:48 ` Jeff Garzik [this message]
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=46E1E35F.1010907@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--cc=jason.d.gaston@intel.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.