All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: [lm-sensors] [GIT PATCH] I2C and hwmon fixes for 2.6.18-rc1
Date: Wed, 26 Jul 2006 20:01:21 +0000	[thread overview]
Message-ID: <20060726220121.89fda898.khali@linux-fr.org> (raw)
In-Reply-To: <20060724193808.GA9244@suse.de>

Hi Greg,

> On Mon, Jul 24, 2006 at 09:21:46PM +0200, Jean Delvare wrote:
> > > Here are some i2c and hwmon fixes for 2.6.18-rc1.  They fix quite a few
> > > bugs and update the documentation.
> > > (...)
> > > The full patch series will sent to the sensors mailing list, if anyone
> > > wants to see them.
> > 
> > Which is quite unfortunate because we now have a new mailing list
> > dedicated to i2c [1], where the i2c patches would fit better. Is it
> > possible to send the i2c patches to the i2c list next time? And the
> > hwmon patches to the sensors list as before.
> 
> I can do that if you want me to split up the hwmon and i2c patches into
> two different set of patches for Linus to pull from.  If you think it's
> worth it, I will.

Yes, please. Else people will never get that i2c and hwmon are
different things (although they intersect.)

Thanks,
-- 
Jean Delvare


WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [GIT PATCH] I2C and hwmon fixes for 2.6.18-rc1
Date: Wed, 26 Jul 2006 22:01:21 +0200	[thread overview]
Message-ID: <20060726220121.89fda898.khali@linux-fr.org> (raw)
In-Reply-To: <20060724193808.GA9244@suse.de>

Hi Greg,

> On Mon, Jul 24, 2006 at 09:21:46PM +0200, Jean Delvare wrote:
> > > Here are some i2c and hwmon fixes for 2.6.18-rc1.  They fix quite a few
> > > bugs and update the documentation.
> > > (...)
> > > The full patch series will sent to the sensors mailing list, if anyone
> > > wants to see them.
> > 
> > Which is quite unfortunate because we now have a new mailing list
> > dedicated to i2c [1], where the i2c patches would fit better. Is it
> > possible to send the i2c patches to the i2c list next time? And the
> > hwmon patches to the sensors list as before.
> 
> I can do that if you want me to split up the hwmon and i2c patches into
> two different set of patches for Linus to pull from.  If you think it's
> worth it, I will.

Yes, please. Else people will never get that i2c and hwmon are
different things (although they intersect.)

Thanks,
-- 
Jean Delvare

  reply	other threads:[~2006-07-26 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 23:23 [lm-sensors] [GIT PATCH] I2C and hwmon fixes for 2.6.18-rc1 Greg KH
2006-07-12 23:23 ` Greg KH
2006-07-24 19:21 ` [lm-sensors] " Jean Delvare
2006-07-24 19:21   ` Jean Delvare
2006-07-24 19:38   ` [lm-sensors] " Greg KH
2006-07-24 19:38     ` Greg KH
2006-07-26 20:01     ` Jean Delvare [this message]
2006-07-26 20:01       ` Jean Delvare

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=20060726220121.89fda898.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.