1. 11 Jul, 2014 1 commit
  2. 26 Nov, 2013 5 commits
  3. 29 Jun, 2013 1 commit
  4. 01 May, 2013 1 commit
  5. 09 Apr, 2013 1 commit
    • Al Viro's avatar
      procfs: new helper - PDE_DATA(inode) · d9dda78b
      Al Viro authored
      The only part of proc_dir_entry the code outside of fs/proc
      really cares about is PDE(inode)->data.  Provide a helper
      for that; static inline for now, eventually will be moved
      to fs/proc, along with the knowledge of struct proc_dir_entry
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
  6. 22 Feb, 2013 1 commit
  7. 03 Jan, 2013 1 commit
  8. 15 Jul, 2012 1 commit
  9. 02 Jan, 2012 1 commit
  10. 31 Oct, 2011 1 commit
  11. 24 Oct, 2011 1 commit
  12. 22 Sep, 2011 1 commit
    • Geert Uytterhoeven's avatar
      zorro: Defer device_register() until all devices have been identified · a7f4d00a
      Geert Uytterhoeven authored
      As the Amiga Zorro II address space is limited to 8.5 MiB and Zorro
      devices can contain only one BAR, several Amiga Zorro II expansion
      boards (mainly graphics cards) contain multiple Zorro devices: a small
      one for the control registers and one (or more) for the graphics memory.
      The conversion of cirrusfb to the new driver framework introduced a
      regression: the driver contains a zorro_driver for the first Zorro
      device, and uses the (old) zorro_find_device() call to find the second
      Zorro device.
      However, as the Zorro core calls device_register() as soon as a Zorro
      device is identified, it may not have identified the second Zorro device
      belonging to the same physical Zorro expansion card.  Hence cirrusfb
      could no longer find the second part of the Picasso II graphics card,
      causing a NULL pointer dereference.
      Defer the registration of Zorro devices with the driver framework until
      all Zorro devices have been identified to fix this.
      Note that the alternative solution (modifying cirrusfb to register a
      zorro_driver for all Zorro devices belonging to a graphics card, instead
      of only for the first one, and adding a synchronization mechanism to
      defer initialization until all have been found), is not an option, as on
      some cards one device may be optional (e.g.  the second bank of 2 MiB of
      graphics memory on the Picasso IV in Zorro II mode).
      Reported-by: default avatarIngo Jürgensmann <ij@2011.bluespice.org>
      Signed-off-by: default avatarGeert Uytterhoeven <geert@linux-m68k.org>
      Cc: stable@kernel.org
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  13. 17 Nov, 2010 1 commit
  14. 22 Oct, 2010 1 commit
  15. 09 Aug, 2010 2 commits
  16. 21 May, 2010 1 commit
  17. 17 May, 2010 2 commits
  18. 15 Feb, 2010 1 commit
  19. 06 Dec, 2009 1 commit
  20. 24 Mar, 2009 1 commit
  21. 12 Jan, 2009 3 commits
  22. 24 Jul, 2008 1 commit
  23. 20 Jul, 2008 3 commits
  24. 29 Apr, 2008 3 commits
  25. 26 Nov, 2007 1 commit
  26. 19 Oct, 2007 1 commit
  27. 22 Aug, 2007 1 commit
  28. 11 Jul, 2007 1 commit
    • Zhang Rui's avatar
      sysfs: add parameter "struct bin_attribute *" in .read/.write methods for sysfs binary attributes · 91a69029
      Zhang Rui authored
      Well, first of all, I don't want to change so many files either.
      What I do:
      Adding a new parameter "struct bin_attribute *" in the
      .read/.write methods for the sysfs binary attributes.
      In fact, only the four lines change in fs/sysfs/bin.c and
      include/linux/sysfs.h do the real work.
      But I have to update all the files that use binary attributes
      to make them compatible with the new .read and .write methods.
      I'm not sure if I missed any. :(
      Why I do this:
      For a sysfs attribute, we can get a pointer pointing to the
      struct attribute in the .show/.store method,
      while we can't do this for the binary attributes.
      I don't know why this is different, but this does make it not
      so handy to use the binary attributes as the regular ones.
      So I think this patch is reasonable. :)
      Who benefits from it:
      The patch that exposes ACPI tables in sysfs
      requires such an improvement.
      All the table binary attributes share the same .read method.
      Parameter "struct bin_attribute *" is used to get
      the table signature and instance number which are used to
      distinguish different ACPI table binary attributes.
      Without this parameter, we need to offer different .read methods
      for different ACPI table binary attributes.
      This is impossible as there are various ACPI tables on different
      platforms, and we don't know what they are until they are loaded.
      Signed-off-by: default avatarZhang Rui <rui.zhang@intel.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>