From: Jeff Garzik <garzik@havoc.gtf.org>
To: Bruce Harada <harada@mbr.sphere.ne.jp>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Misc ICH ID changes - revised
Date: Thu, 31 Jan 2002 14:10:25 -0500 [thread overview]
Message-ID: <20020131141025.E669@havoc.gtf.org> (raw)
In-Reply-To: <20020131224122.59d1de9e.bruce@ask.ne.jp> <E16WIFn-0002Iy-00@the-village.bc.nu> <20020201022958.7b58493f.harada@mbr.sphere.ne.jp>
In-Reply-To: <20020201022958.7b58493f.harada@mbr.sphere.ne.jp>; from harada@mbr.sphere.ne.jp on Fri, Feb 01, 2002 at 02:29:58AM +0900
On Fri, Feb 01, 2002 at 02:29:58AM +0900, Bruce Harada wrote:
>
> Sorry, I could have put that better... all I was talking about there was
> renaming the #defines to more closely reflect Intel docs, which don't refer
> to the ICH IDE stuff as PIIX4s. Let me know if I should drop that bit.
>
> Anyway, I've added a little more - some of the ICH3 IDs, and a few user messages.
Would it be possible to produce two patches, the first adding new ids,
and the second doing the rename you want?
The first can be applied quickly, the second is cleanup and might be
delayed a bit before going in, if we indeed do want to do the renames.
Jeff
next prev parent reply other threads:[~2002-01-31 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 13:41 [PATCH] Misc ICH ID changes Bruce Harada
2002-01-31 14:31 ` Alan Cox
2002-01-31 17:29 ` [PATCH] Misc ICH ID changes - revised Bruce Harada
2002-01-31 19:10 ` Jeff Garzik [this message]
2002-02-01 0:54 ` [PATCH] Misc ICH ID changes/additions Bruce Harada
2002-02-07 10:45 ` Kurt Garloff
2002-02-10 18:02 ` Bruce Harada
2002-02-01 0:57 ` [PATCH] PIIX4->ICH #define changes/additions Bruce Harada
2002-02-01 1:00 ` [PATCH] PIIX4->ICH user message changes Bruce Harada
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=20020131141025.E669@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=harada@mbr.sphere.ne.jp \
--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
all inboxes | Powered by JetHome®