From: Michael Hunold <hunold@convergence.de>
To: Greg KH <greg@kroah.com>
Cc: Jean Delvare <khali@linux-fr.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][2.6]
Date: Thu, 06 May 2004 10:17:19 +0200 [thread overview]
Message-ID: <4099F48F.2090307@convergence.de> (raw)
In-Reply-To: <20040505175323.GA13088@kroah.com>
Hello Greg,
On 05/05/04 19:53, Greg KH wrote:
>>I think these things are unquestionable and don't make any functional
>>changes to the code, so this should be applied to 2.6 now.
> Now as in I'll add it to my i2c tree, which will get picked up by -mm
> and let it bake a bit and then pushed to Linus, yes.
This is how I meant it.
Quoting your other mail:
> Looks good, I've applied this to my trees, and it will show up in the
> next -mm release.
Ok, thanks. As my time permits it, I'll prepare patches to add class
entries to the i2c adapters and i2c clients.
But I won't be sad if the sensors people make the changes to their
drivers themselves. ;-)
(ie. mostly remove
> if (!(adapter->class & I2C_CLASS_SMBUS))
> return 0;
from the xxx_attach_adapter() funtion (the check will be done in the
i2c-core and add a .class = I2C_CLASS_SMBUS to the xxx_driver static
variable)
> greg k-h
CU
Michael.
next prev parent reply other threads:[~2004-05-06 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 17:27 [PATCH][2.6] Michael Hunold
2005-05-19 6:24 ` [PATCH][2.6] Michael Hunold
2004-05-05 17:53 ` [PATCH][2.6] Greg KH
2005-05-19 6:24 ` [PATCH][2.6] Greg KH
2004-05-06 8:17 ` Michael Hunold [this message]
2004-05-05 23:13 ` [PATCH][2.6] Greg KH
2005-05-19 6:24 ` [PATCH][2.6] Greg KH
2004-05-06 19:34 ` [PATCH][2.6] Jean Delvare
2005-05-19 6:24 ` [PATCH][2.6] Jean Delvare
2004-05-09 15:48 ` [PATCH 2.6] Rename hardware monitoring I2C class Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-05-11 20:44 ` Greg KH
2005-05-19 6:24 ` 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=4099F48F.2090307@convergence.de \
--to=hunold@convergence.de \
--cc=greg@kroah.com \
--cc=khali@linux-fr.org \
--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 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.