From: Jeff Garzik <jeff@garzik.org>
To: JosephChan@via.com.tw
Cc: linux-ide@vger.kernel.org, stable@kernel.org,
alan@lxorguk.ukuu.org.uk, tj@kernel.org
Subject: Re: [Patch 1/1 v3 RESEND] sata_via.c: Remove redundant device ID for VIA VT8261
Date: Tue, 03 Nov 2009 16:17:46 -0500 [thread overview]
Message-ID: <4AF09DFA.2010503@garzik.org> (raw)
In-Reply-To: <C80EF34A3D2E494DBAF9AC29C7AE4EB80A353BCF@exchtp03.taipei.via.com.tw>
On 11/02/2009 06:36 AM, JosephChan@via.com.tw wrote:
> Re-send.
>
> Just remove redundant device ID for VIA VT8261.
> The device ID 0x9000 and 0x9040 are redundant (for VT8261).
> The 0x9040 is reserved for other usage.
>
> Signed-off-by: Joseph Chan<josephchan@via.com.tw>
applied
prev parent reply other threads:[~2009-11-03 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 11:36 [Patch 1/1 v3 RESEND] sata_via.c: Remove redundant device ID for VIA VT8261 JosephChan
2009-11-03 21:17 ` 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=4AF09DFA.2010503@garzik.org \
--to=jeff@garzik.org \
--cc=JosephChan@via.com.tw \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).