From 5290cd9de4828d416e6c6a365243185b12ddd7da Mon Sep 17 00:00:00 2001 From: Jean Delvare Date: Sun, 6 Dec 2009 17:06:30 +0100 Subject: [PATCH] --- yaml --- r: 172373 b: refs/heads/master c: 6471b68982d3bb1a593c3e183c804ecf830125d3 h: refs/heads/master i: 172371: 7d88d19c642e892adcc2aac96f0981342fb377d3 v: v3 --- [refs] | 2 +- trunk/Documentation/i2c/i2c-stub | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/[refs] b/[refs] index 919091b4ea52..10e616307ea0 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 38f41f282f1f88b4038f019de51cb95984e569d5 +refs/heads/master: 6471b68982d3bb1a593c3e183c804ecf830125d3 diff --git a/trunk/Documentation/i2c/i2c-stub b/trunk/Documentation/i2c/i2c-stub index 326d1ee81e0e..fa4b669c166b 100644 --- a/trunk/Documentation/i2c/i2c-stub +++ b/trunk/Documentation/i2c/i2c-stub @@ -21,8 +21,8 @@ EEPROMs, among others. The typical use-case is like this: 1. load this module - 2. use i2cset (from lm_sensors project) to pre-load some data - 3. load the target sensors chip driver module + 2. use i2cset (from the i2c-tools project) to pre-load some data + 3. load the target chip driver module 4. observe its behavior in the kernel log There's a script named i2c-stub-from-dump in the i2c-tools package which