From: "Jean Delvare" <khali@linux-fr.org>
To: jdgaston@snoqualmie.dp.intel.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ICH6/6300ESB i2c support
Date: Thu, 13 May 2004 10:05:06 +0200 (CEST) [thread overview]
Message-ID: <200405130805.i4D856M0055748@zone3.gcu-squad.org> (raw)
Hi Jason,
A few comments on your patch:
> This patch adds DID support for ICH6 and 6300ESB to i2c-i801.c(SMBus). In
> order to add this support I needed to patch pci_ids.h with the SMBus DID's.
> To keep things orginized I renumbered the ICH6 and ESB entries in pci_ids.h.
> I then patched the piix IDE and i810 audio drivers to reflect the updated
> #define's. I also removed an error from irq.c; there was a reference to a
> 6300ESB DID that does not exist. This patch is against the 2.6.6 kernel.
To me, there are two different things here and you should split your
patch accordingly for clarity. The renumbering of the entries should go
in a first patch, then the new devices support in i2c-i801 in a second.
I would also suggest that you follow the common habit to name the Intel
82801 chips after their numerical name (82801AA. 82801BA, etc...) and
not their nickname (ICH, ICH2...) in both the entries and the comments.
Not that it is absolulety better, but that's the way we did so far, so
why change now?
I would appreciate it if you could submit a similar patch for the 2.4
version of the i2c-i801 driver as held in the lm_sensors project.
Thanks.
Jean Delvare
--
Jean "Khali" Delvare
http://khali.linux-fr.org/
next reply other threads:[~2004-05-13 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 8:05 Jean Delvare [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-13 19:46 Gaston, Jason D
2004-05-13 20:57 ` Jean Delvare
2004-05-12 19:52 jdgaston
2004-05-14 21:59 ` Greg KH
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=200405130805.i4D856M0055748@zone3.gcu-squad.org \
--to=khali@linux-fr.org \
--cc=jdgaston@snoqualmie.dp.intel.com \
--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®