FAILED: patch "[PATCH] i2c: slave: fix the example how to instantiate from userspace" failed to apply to 4.0-stable tree

PATCH [email protected] 1 participant 1 message Jun 19, 2015

Subsystems (2)

Stable branch I2C

lore

Share & tools

lore

[email protected]

author maintainer

2015-06-19 18:22 UTC #0 lore raw

The patch below does not apply to the 4.0-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.

thanks,

greg k-h

------------------ original commit in Linus's tree ------------------

Quoted 1 line

From 8366610283d08564f65a1af2ec8458df08418727 Mon Sep 17 00:00:00 2001

From: Wolfram Sang <[email protected]>
Date: Mon, 15 Jun 2015 19:51:46 +0200
Subject: [PATCH] i2c: slave: fix the example how to instantiate from userspace

I copied the wrong shell code into the documentation. Sorry to all who tried to get sense out of this current example :/ Slight rewording while we are here.

Reported-by Tim Bakker <[email protected]>

Signed-off-by Wolfram Sang <[email protected]>

Cc [email protected]

Documentation/i2c/slave-interface +3 -3

index 389bb5d61854..b228ca54bcf4 100644
@@ -31,10 +31,10 @@ User manual
 ===========
 
 I2C slave backends behave like standard I2C clients. So, you can instantiate
-them like described in the document 'instantiating-devices'. A quick example
-for instantiating the slave-eeprom driver from userspace:
+them as described in the document 'instantiating-devices'. A quick example for
+instantiating the slave-eeprom driver from userspace at address 0x64 on bus 1:
 
-  # echo 0-0064 > /sys/bus/i2c/drivers/i2c-slave-eeprom/bind
+  # echo slave-24c02 0x64 > /sys/bus/i2c/devices/i2c-1/new_device
 
 Each backend should come with separate documentation to describe its specific
 behaviour and setup.

--
To unsubscribe from this list: send the line "unsubscribe stable" in