From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@Stimpy.netroedge.com
Subject: Re: [PATCH] I2C fixes for 2.6.10-rc2
Date: Fri, 19 Nov 2004 14:00:48 -0800 [thread overview]
Message-ID: <20041119220048.GE15956@kroah.com> (raw)
In-Reply-To: <20041119220030.GD15956@kroah.com>
ChangeSet 1.2167, 2004/11/19 09:14:15-08:00, paubert@iram.es
[PATCH] I2C: minor comment fix
It seems so. BTW I hate wrong comments and happened to add one
in my patch. To fix my blunder, can you apply the appended one
line removal on top of Jean's patch.
Signed-off-by: Gabriel Paubert <paubert@iram.es>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
drivers/i2c/i2c-core.c | 1 -
1 files changed, 1 deletion(-)
diff -Nru a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
--- a/drivers/i2c/i2c-core.c 2004-11-19 11:40:37 -08:00
+++ b/drivers/i2c/i2c-core.c 2004-11-19 11:40:37 -08:00
@@ -1021,7 +1021,6 @@
I2C_SMBUS_WORD_DATA,&data);
}
-/* Returns the number of bytes transferred */
s32 i2c_smbus_write_block_data(struct i2c_client *client, u8 command,
u8 length, u8 *values)
{
next prev parent reply other threads:[~2004-11-19 22:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 21:59 [BK PATCH] I2C fixes for 2.6.10-rc2 Greg KH
2004-11-19 22:00 ` [PATCH] " Greg KH
2004-11-19 22:00 ` Greg KH
2004-11-19 22:00 ` Greg KH
2004-11-19 22:00 ` Greg KH [this message]
2004-11-19 22:01 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-12-01 0:12 [BK PATCH] " Greg KH
2004-12-01 0:13 ` [PATCH] " Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` Greg KH
2004-12-01 0:13 ` 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=20041119220048.GE15956@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox