From: greg@kroah.com (Greg KH)
To: Michael Hunold <hunold@linuxtv.org>
Cc: Jean Delvare <khali@linux-fr.org>,
sensors@Stimpy.netroedge.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Adding .class field to struct i2c_client (was Re: [PATCH][2.6]
Date: Thu, 19 May 2005 06:25:17 +0000 [thread overview]
Message-ID: <20040924000202.GO14868@kroah.com> (raw)
In-Reply-To: <415067CB.1020101@linuxtv.org>
On Tue, Sep 21, 2004 at 07:41:31PM +0200, Michael Hunold wrote:
> Please have a look and tell me what you think. The big problem will be,
> that we cannot test all configurations, so it's possible that some
> devices won't be recognized anymore, because the .class entries don't match.
I like the patches. If you get them in a state you like (and drop the
printk(), and use dev_dbg() instead), and send them 1 patch per file
with the Signed-off-by: line, I'll be glad to apply them.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Michael Hunold <hunold@linuxtv.org>
Cc: Jean Delvare <khali@linux-fr.org>,
sensors@Stimpy.netroedge.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Adding .class field to struct i2c_client (was Re: [PATCH][2.6] Add command function to struct i2c_adapter
Date: Thu, 23 Sep 2004 17:02:02 -0700 [thread overview]
Message-ID: <20040924000202.GO14868@kroah.com> (raw)
In-Reply-To: <415067CB.1020101@linuxtv.org>
On Tue, Sep 21, 2004 at 07:41:31PM +0200, Michael Hunold wrote:
> Please have a look and tell me what you think. The big problem will be,
> that we cannot test all configurations, so it's possible that some
> devices won't be recognized anymore, because the .class entries don't match.
I like the patches. If you get them in a state you like (and drop the
printk(), and use dev_dbg() instead), and send them 1 patch per file
with the Signed-off-by: line, I'll be glad to apply them.
thanks,
greg k-h
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 [Fwd: [PATCH][2.6] Add command function to struct i2c_adapter] Michael Hunold
2004-09-21 13:28 ` [PATCH][2.6] Add command function to struct i2c_adapter Jean Delvare
2005-05-19 6:25 ` Jean Delvare
2004-09-21 14:38 ` Michael Hunold
2005-05-19 6:25 ` Michael Hunold
2004-09-21 17:41 ` Adding .class field to struct i2c_client (was " Michael Hunold
2005-05-19 6:25 ` Adding .class field to struct i2c_client (was Re: [PATCH][2.6] Add Michael Hunold
2004-09-21 20:16 ` Adding .class field to struct i2c_client (was Re: [PATCH][2.6] Add command function to struct i2c_adapter Jon Smirl
2005-05-19 6:25 ` Adding .class field to struct i2c_client (was Re: [PATCH][2.6] Jon Smirl
2004-09-24 0:02 ` Greg KH [this message]
2005-05-19 6:25 ` Greg KH
2004-09-24 6:22 ` Adding .class field to struct i2c_client (was Re: [PATCH][2.6] Add command function to struct i2c_adapter Michael Hunold
2005-05-19 6:25 ` Adding .class field to struct i2c_client (was Re: [PATCH][2.6] Michael Hunold
2004-09-24 16:43 ` Adding .class field to struct i2c_client (was Re: [PATCH][2.6] Add command function to struct i2c_adapter Greg KH
2005-05-19 6:25 ` Adding .class field to struct i2c_client (was Re: [PATCH][2.6] 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=20040924000202.GO14868@kroah.com \
--to=greg@kroah.com \
--cc=hunold@linuxtv.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.