Merge tag 'driver-core-3.6-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core

Pull driver core changes from Greg Kroah-Hartman:
 "Here's the big driver core pull request for 3.6-rc1.

  Unlike 3.5, this kernel should be a lot tamer, with the printk changes
  now settled down.  All we have here is some extcon driver updates, w1
  driver updates, a few printk cleanups that weren't needed for 3.5, but
  are good to have now, and some other minor fixes/changes in the driver
  core.

  All of these have been in the linux-next releases for a while now.

  Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>"

* tag 'driver-core-3.6-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (38 commits)
  printk: Export struct log size and member offsets through vmcoreinfo
  Drivers: hv: Change the hex constant to a decimal constant
  driver core: don't trigger uevent after failure
  extcon: MAX77693: Add extcon-max77693 driver to support Maxim MAX77693 MUIC device
  sysfs: fail dentry revalidation after namespace change fix
  sysfs: fail dentry revalidation after namespace change
  extcon: spelling of detach in function doc
  extcon: arizona: Stop microphone detection if we give up on it
  extcon: arizona: Update cable reporting calls and split headset
  PM / Runtime: Do not increment device usage counts before probing
  kmsg - do not flush partial lines when the console is busy
  kmsg - export "continuation record" flag to /dev/kmsg
  kmsg - avoid warning for CONFIG_PRINTK=n compilations
  kmsg - properly print over-long continuation lines
  driver-core: Use kobj_to_dev instead of re-implementing it
  driver-core: Move kobj_to_dev from genhd.h to device.h
  driver core: Move deferred devices to the end of dpm_list before probing
  driver core: move uevent call to driver_register
  driver core: fix shutdown races with probe/remove(v3)
  Extcon: Arizona: Add driver for Wolfson Arizona class devices
  ...

2 files changed, 35 insertions, 9 deletions

diff --git a/Documentation/ABI/stable/sysfs-driver-w1_ds28e04 b/Documentation/ABI/stable/sysfs-driver-w1_ds28e04
new file mode 100644
index 000000000000..26579ee868c9
--- /dev/null
+++ b/Documentation/ABI/stable/sysfs-driver-w1_ds28e04
@@ -0,0 +1,15 @@
+What:           /sys/bus/w1/devices/.../pio
+Date:           May 2012
+Contact:        Markus Franke <franm@hrz.tu-chemnitz.de>
+Description:    read/write the contents of the two PIO's of the DS28E04-100
+                see Documentation/w1/slaves/w1_ds28e04 for detailed information
+Users:          any user space application which wants to communicate with DS28E04-100
+
+
+
+What:           /sys/bus/w1/devices/.../eeprom
+Date:           May 2012
+Contact:        Markus Franke <franm@hrz.tu-chemnitz.de>
+Description:    read/write the contents of the EEPROM memory of the DS28E04-100
+                see Documentation/w1/slaves/w1_ds28e04 for detailed information
+Users:          any user space application which wants to communicate with DS28E04-100
diff --git a/Documentation/ABI/testing/dev-kmsg b/Documentation/ABI/testing/dev-kmsg
index 281ecc5f9709..7e7e07a82e0e 100644
--- a/Documentation/ABI/testing/dev-kmsg
+++ b/Documentation/ABI/testing/dev-kmsg
@@ -58,16 +58,18 @@ Description:	The /dev/kmsg character device node provides userspace access
 
                 The output format consists of a prefix carrying the syslog
                 prefix including priority and facility, the 64 bit message
-                sequence number and the monotonic timestamp in microseconds.
-                The values are separated by a ','. Future extensions might
-                add more comma separated values before the terminating ';'.
-                Unknown values should be gracefully ignored.
+                sequence number and the monotonic timestamp in microseconds,
+                and a flag field. All fields are separated by a ','.
+
+                Future extensions might add more comma separated values before
+                the terminating ';'. Unknown fields and values should be
+                gracefully ignored.
 
                 The human readable text string starts directly after the ';'
                 and is terminated by a '\n'. Untrusted values derived from
                 hardware or other facilities are printed, therefore
-                all non-printable characters in the log message are escaped
-                by "\x00" C-style hex encoding.
+                all non-printable characters and '\' itself in the log message
+                are escaped by "\x00" C-style hex encoding.
 
                 A line starting with ' ', is a continuation line, adding
                 key/value pairs to the log message, which provide the machine
@@ -75,11 +77,11 @@ Description:	The /dev/kmsg character device node provides userspace access
                 userspace.
 
                 Example:
-                7,160,424069;pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7] (ignored)
+                7,160,424069,-;pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7] (ignored)
                  SUBSYSTEM=acpi
                  DEVICE=+acpi:PNP0A03:00
-                6,339,5140900;NET: Registered protocol family 10
-                30,340,5690716;udevd[80]: starting version 181
+                6,339,5140900,-;NET: Registered protocol family 10
+                30,340,5690716,-;udevd[80]: starting version 181
 
                 The DEVICE= key uniquely identifies devices the following way:
                   b12:8        - block dev_t
@@ -87,4 +89,13 @@ Description:	The /dev/kmsg character device node provides userspace access
                   n8           - netdev ifindex
                   +sound:card0 - subsystem:devname
 
+                The flags field carries '-' by default. A 'c' indicates a
+                fragment of a line. All following fragments are flagged with
+                '+'. Note, that these hints about continuation lines are not
+                neccessarily correct, and the stream could be interleaved with
+                unrelated messages, but merging the lines in the output
+                usually produces better human readable results. A similar
+                logic is used internally when messages are printed to the
+                console, /proc/kmsg or the syslog() syscall.
+
 Users:          dmesg(1), userspace kernel log consumers