From: Greg KH <greg@kroah.com>
To: Justin Thiessen <jthiessen@penguincomputing.com>
Cc: linux-kernel@vger.kernel.org, sensors@Stimpy.netroedge.com,
phil@netroedge.com
Subject: Re: [PATCH] 2.6 lm85.c driver update
Date: Mon, 8 Nov 2004 16:49:18 -0800 [thread overview]
Message-ID: <20041109004918.GA25651@kroah.com> (raw)
In-Reply-To: <20041105222546.GA31538@penguincomputing.com>
On Fri, Nov 05, 2004 at 02:25:46PM -0800, Justin Thiessen wrote:
> On Fri, Nov 05, 2004 at 01:48:41PM -0800, Greg KH wrote:
> > On Mon, Oct 25, 2004 at 03:05:26PM -0700, Justin Thiessen wrote:
> > > On Mon, Oct 25, 2004 at 10:59:59PM +0200, Jean Delvare wrote:
> > > > > > Hm, there are a number of rejects in this patch. Care to resync up
> > > > > > with the next kernel release and resend this?
> > > > >
> > > > > Ok, try this:
> > > > >
> > > > > signed off by: Justin Thiessen <jthiessen@penguincomputing.com>
> > > > >
> > > > > patch for kernel 2.6.X lm85 driver follows:
>
> <snip>
>
> > Applied, thanks.
> >
> > But now I get the following build warnings:
> >
> > drivers/i2c/chips/lm85.c:220: warning: 'SMOOTH_TO_REG' defined but not used
> > drivers/i2c/chips/lm85.c:236: warning: 'SPINUP_TO_REG' defined but not used
> >
> > Care to send me a patch to fix them up?
>
> Ok.
>
> Justin Thiessen
>
> Signed off by Justin Thiessen <jthiessen@penguincomputing.com>
Applied, thanks.
greg k-h
prev parent reply other threads:[~2004-11-09 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041004200943.GE22290@penguincomputing.com>
[not found] ` <20041019222920.GJ9521@kroah.com>
2004-10-25 20:36 ` [PATCH] 2.6 lm85.c driver update Justin Thiessen
2004-10-25 20:59 ` Jean Delvare
[not found] ` <20041025220526.GC19053@penguincomputing.com>
2004-11-05 21:48 ` Greg KH
2004-11-05 22:25 ` Justin Thiessen
2004-11-09 0:49 ` Greg KH [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=20041109004918.GA25651@kroah.com \
--to=greg@kroah.com \
--cc=jthiessen@penguincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@netroedge.com \
--cc=sensors@Stimpy.netroedge.com \
/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