From: mhoffman@lightlink.com (Mark M. Hoffman)
To: lm-sensors@vger.kernel.org
Subject: [PATCH 2.6] I2C: Add byte commands to i2c-stub
Date: Thu, 19 May 2005 06:25:28 +0000 [thread overview]
Message-ID: <20050102214101.GC17759@jupiter.solarsys.private> (raw)
In-Reply-To: <20041226151327.56a80b7c.khali@linux-fr.org>
* Jean Delvare <khali@linux-fr.org> [2004-12-26 15:13:27 +0100]:
> Hi Mark, all,
>
> While working on EEPROMs, DDC/EDID and the like these last few days, I
> wanted to use your i2c-stub driver to test my code. However, I noticed
> that it wouldn't handle byte commands, while both i2cdetect and the
> eeprom driver need it for proper operation. Thus I added this
> functionality to the driver. What do you think about it?
>
> Greg, please apply to your tree unless Mark objects.
No objection here - thanks!
And since this topic has come up... I'll look into using the newly proposed
debugfs here instead of printk. Hopefully the new usbmon [1] is a good model?
[1] http://kerneltrap.org/node/4449
Regards,
--
Mark M. Hoffman
mhoffman@lightlink.com
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 [PATCH 2.6] I2C: Add byte commands to i2c-stub Jean Delvare
2005-05-19 6:25 ` Mark M. Hoffman [this message]
2005-05-19 6:25 ` 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=20050102214101.GC17759@jupiter.solarsys.private \
--to=mhoffman@lightlink.com \
--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.