From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] What about i2c_smbus_read_block_data() ?
Date: Sun, 08 Apr 2007 09:26:02 +0000 [thread overview]
Message-ID: <200704081126.02563.hjk@linutronix.de> (raw)
In-Reply-To: <200704042149.21264.hjk@linutronix.de>
Am Sonntag 08 April 2007 10:58 schrieb Jean Delvare:
>
> I have a different variant of this patch in my local tree, which takes
> the i2c-core changes that happened in the meantime into account. I'm
> attaching it to this post if someone want to take a look and/or
> comment.
Looks allright to me.
> In fact I think I'll schedule this patch for merge into 2.6.22
> regardless of the state of the lm93 driver patch.
Good idea. I will submit a first version of the LM93 patch next Thursday
or Friday. It's ready, but I cannot test it until then.
> I'm a bit tired to
> have to maintain that patch off-tree and to see people waste their time
> wondering where that function has gone, searching the mailing list for
> explanations, finding the patch and resubmitting it. We all have better
> things to do.
I second that.
>
> Anyway, the key point for Hans-Jürgen is: you can assume that function
> i2c_smbus_read_block_data() will be available to you when your lm93
> driver patch is merged upstream.
Fine.
Thanks,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2007-04-08 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 19:49 [lm-sensors] What about i2c_smbus_read_block_data() ? Hans-Jürgen Koch
2007-04-04 21:32 ` Hans-Jürgen Koch
2007-04-05 2:42 ` Mark M. Hoffman
2007-04-08 8:58 ` Jean Delvare
2007-04-08 9:26 ` Hans-Jürgen Koch [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=200704081126.02563.hjk@linutronix.de \
--to=hjk@linutronix.de \
--cc=lm-sensors@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.