From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: JosephChan@via.com.tw, linux-ide@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, postmaster@vger.kernel.org
Subject: Re: [Patch 1/1] sata_via.c: Remove redundant device ID for VT8261
Date: Thu, 15 Oct 2009 03:36:10 -0400 [thread overview]
Message-ID: <4AD6D0EA.6090400@garzik.org> (raw)
In-Reply-To: <4AD6CCF1.4030501@kernel.org>
On 10/15/2009 03:19 AM, Tejun Heo wrote:
> JosephChan@via.com.tw wrote:
>> Just remove redundant device ID for VT8261.
>>
>> Signed-off-by: Joseph Chan<josephchan@via.com.tw>
>
> Looks okay to me.
>
>> --- a/drivers/ata/sata_via.c 2009-10-15 21:38:14.000000000 +0800
>> +++ b/drivers/ata/sata_via.c 2009-10-15 21:38:28.000000000 +0800
>> @@ -93,7 +93,6 @@
>> { PCI_VDEVICE(VIA, 0x7372), vt6420 },
>> { PCI_VDEVICE(VIA, 0x5287), vt8251 }, /* 2 sata chnls (Master/Slave) */
>> { PCI_VDEVICE(VIA, 0x9000), vt8251 },
>> - { PCI_VDEVICE(VIA, 0x9040), vt8251 },
>>
>> { } /* terminate list */
>> };
>>
>> N�����r��y���b�X��ǧv�^�){.n�+����{��ע��^n�r��z�\x1a��h����&��\x1e�G���h�\x03(�階�ݢj"��\x1a�^[m�����z�ޖ���f���h���~�mml==
>
> But, what's the above garbled line?
(cc'ing postmaster@vger)
It is interesting that Joseph's email directly to me was OK, but the
copy passing through vger.kernel.org list software included this garbled
line.
Joseph's email was base64-encoded, and vger just got new mailing list
software in the past year or so... so I wonder if this is a vger bug?
Jeff
next prev parent reply other threads:[~2009-10-15 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 7:10 [Patch 1/1] sata_via.c: Remove redundant device ID for VT8261 JosephChan
2009-10-15 7:16 ` Jeff Garzik
2009-10-15 7:24 ` JosephChan
2009-10-15 7:19 ` Tejun Heo
2009-10-15 7:36 ` Jeff Garzik [this message]
2009-10-15 7:52 ` JosephChan
2009-10-15 15:37 ` David Miller
2009-10-15 15:46 ` Jeff Garzik
2009-10-15 19:15 ` David Miller
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=4AD6D0EA.6090400@garzik.org \
--to=jeff@garzik.org \
--cc=JosephChan@via.com.tw \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=postmaster@vger.kernel.org \
--cc=tj@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.