From 9481a5d6e1579f47d8732cd9f09c3be29bcc3924 Mon Sep 17 00:00:00 2001 From: Bart Van Assche Date: Tue, 23 Aug 2011 19:28:43 +0200 Subject: [PATCH] --- yaml --- r: 264871 b: refs/heads/master c: b7565fa3a4b84460ce1765cc468700a6bfd82746 h: refs/heads/master i: 264869: c0f183e634a8e6c31d2bfed025c7b408fe1481a7 264867: caf63ede7f0c5a4661373795bcbfe061c87f7e20 264863: 16b6b6680d276ccd1c75a35d04826d480be897d2 v: v3 --- [refs] | 2 +- trunk/Documentation/driver-model/binding.txt | 4 ---- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/[refs] b/[refs] index 99c7ce5aa544..97b0a769fa24 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: d58cb9cc8a46c9e539cbf8007cd5ede3c09c3524 +refs/heads/master: b7565fa3a4b84460ce1765cc468700a6bfd82746 diff --git a/trunk/Documentation/driver-model/binding.txt b/trunk/Documentation/driver-model/binding.txt index f7ec9d625bfc..abfc8e290d53 100644 --- a/trunk/Documentation/driver-model/binding.txt +++ b/trunk/Documentation/driver-model/binding.txt @@ -48,10 +48,6 @@ devclass_add_device is called to enumerate the device within the class and actually register it with the class, which happens with the class's register_dev callback. -NOTE: The device class structures and core routines to manipulate them -are not in the mainline kernel, so the discussion is still a bit -speculative. - Driver ~~~~~~