From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Colin Leroy <colin@colino.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] therm_adt7467 update
Date: Fri, 12 Mar 2004 09:45:41 +1100 [thread overview]
Message-ID: <1079045140.9745.295.camel@gaston> (raw)
In-Reply-To: <00e401c40776$2a37eca0$3cc8a8c0@epro.dom>
On Fri, 2004-03-12 at 01:35, Colin Leroy wrote:
> Hi,
>
> the fan driver I wrote for adt746x looks like it only handles the adt7467
> chip found in iBooks G4; but it also handles the adt7460 chip found in the
> Powerbook G4 Alu.
> Here's a patch that renames the file to therm_adt746x.c and updates
> Kconfig and Makefile. I also changed a few lines in therm_adt746x.c after
> renaming it (the patch contains these), the diff is here for clarity:
Ok, I'll look into getting that upstream. Renaming things is a bit
nasty (makes big patch for little changes) unless Linus does
directly a "bk mv" in his tree..
Ben.
next prev parent reply other threads:[~2004-03-11 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 14:35 [PATCH] therm_adt7467 update Colin Leroy
2004-03-11 22:45 ` Benjamin Herrenschmidt [this message]
2004-03-13 15:33 ` Colin Leroy
2004-03-15 23:49 ` Benjamin Herrenschmidt
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=1079045140.9745.295.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=colin@colino.net \
--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