1. 13 Apr, 2009 1 commit
  2. 28 Mar, 2009 3 commits
  3. 24 Mar, 2009 1 commit
    • Ming Lei's avatar
      Driver core: implement uevent suppress in kobject · f67f129e
      Ming Lei authored
      
      
      This patch implements uevent suppress in kobject and removes it
      from struct device, based on the following ideas:
      
      1,Uevent sending should be one attribute of kobject, so suppressing it
      in kobject layer is more natural than in device layer. By this way,
      we can do it for other objects embedded with kobject.
      
      2,It may save several bytes for each instance of struct device.(On my
      omap3(32bit ARM) based box, can save 8bytes per device object)
      
      This patch also introduces dev_set|get_uevent_suppress() helpers to
      set and query uevent_suppress attribute in case to help kobject
      as private part of struct device in future.
      
      [This version is against the latest driver-core patch set of Greg,please
      ignore the last version.]
      Signed-off-by: default avatarMing Lei <tom.leiming@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      f67f129e
  4. 24 Feb, 2009 1 commit
  5. 07 Jan, 2009 1 commit
    • Kay Sievers's avatar
      i2c: Replace bus_id with dev_name(), dev_set_name() · 27d9c183
      Kay Sievers authored
      
      
      This patch is part of a larger patch series which will remove
      the "char bus_id[20]" name string from struct device. The device
      name is managed in the kobject anyway, and without any size
      limitation, and just needlessly copied into "struct device".
      
      To set and read the device name dev_name(dev) and dev_set_name(dev)
      must be used. If your code uses static kobjects, which it shouldn't
      do, "const char *init_name" can be used to statically provide the
      name the registered device should have. At registration time, the
      init_name field is cleared, to enforce the use of dev_name(dev) to
      access the device name at a later time.
      
      We need to get rid of all occurrences of bus_id in the entire tree
      to be able to enable the new interface. Please apply this patch,
      and possibly convert any remaining remaining occurrences of bus_id.
      
      We want to submit a patch to -next, which will remove bus_id from
      "struct device", to find the remaining pieces to convert, and finally
      switch over to the new api, which will remove the 20 bytes array
      and does no longer have a size limitation.
      Acked-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: default avatarKay Sievers <kay.sievers@vrfy.org>
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      27d9c183
  6. 28 Nov, 2008 1 commit
  7. 22 Oct, 2008 1 commit
  8. 14 Oct, 2008 3 commits
  9. 28 Aug, 2008 2 commits
  10. 10 Aug, 2008 2 commits
  11. 21 Jul, 2008 1 commit
  12. 16 Jul, 2008 1 commit
  13. 14 Jul, 2008 12 commits
  14. 18 May, 2008 1 commit
  15. 11 May, 2008 1 commit
    • Jean Delvare's avatar
      i2c: Match dummy devices by type · 60b129d7
      Jean Delvare authored
      
      
      As the old driver_name/type matching scheme is going away soon, change
      the dummy device mechanism to use the new matching scheme.
      
      This has the downside that dummy i2c clients can no longer choose
      their name, they'll all appear as "dummy" in sysfs and in log
      messages. I don't think it is a problem in practice though, as there
      is little reason to use these i2c clients to log messages.
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      60b129d7
  16. 29 Apr, 2008 1 commit
    • Jean Delvare's avatar
      i2c: Add support for device alias names · d2653e92
      Jean Delvare authored
      
      
      Based on earlier work by Jon Smirl and Jochen Friedrich.
      
      This patch allows new-style i2c chip drivers to have alias names using
      the official kernel aliasing system and MODULE_DEVICE_TABLE(). At this
      point, the old i2c driver binding scheme (driver_name/type) is still
      supported.
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Cc: Jochen Friedrich <jochen@scram.de>
      Cc: Jon Smirl <jonsmirl@gmail.com>
      Cc: Kay Sievers <kay.sievers@vrfy.org>
      d2653e92
  17. 22 Apr, 2008 1 commit
  18. 18 Apr, 2008 1 commit
  19. 23 Mar, 2008 1 commit
    • Randy Dunlap's avatar
      i2c: Fix docbook problem · 8c07e46f
      Randy Dunlap authored
      
      
      Sometimes kernel-doc and xmlto conspire to create output that is invalid
      and causes problems.  Until I know a real/better solution, change the
      source code that causes this.
      
      If anyone has better fixes or can just explain what is happening here,
      that would be great.
      
      xmlto: input does not validate (status 1)
      mmotm-2008-0314-1449/Documentation/DocBook/kernel-api.xml:71468: parser error : Opening and ending tag mismatch: programlisting line 71464 and para
         </para><para>
                ^
      mmotm-2008-0314-1449/Documentation/DocBook/kernel-api.xml:71480: parser error : Opening and ending tag mismatch: para line 71473 and programlisting
      </programlisting></informalexample>
                       ^
      make[1]: *** [Documentation/DocBook/kernel-api.html] Error 1
      Signed-off-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      8c07e46f
  20. 12 Mar, 2008 1 commit
  21. 27 Jan, 2008 3 commits