1. 07 Dec, 2017 2 commits
    • Greg Kroah-Hartman's avatar
      driver core: Remove redundant license text · 32825709
      Greg Kroah-Hartman authored
      Now that the SPDX tag is in all driver core files, that identifies the
      license in a specific and legally-defined manner.  So the extra GPL text
      wording can be removed as it is no longer needed at all.
      This is done on a quest to remove the 700+ different ways that files in
      the kernel describe the GPL license text.  And there's unneeded stuff
      like the address (sometimes incorrect) for the FSF which is never
      No copyright headers or other non-license-description text was removed.
      Cc: Johannes Berg <johannes@sipsolutions.net>
      Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
    • Greg Kroah-Hartman's avatar
      driver core: add SPDX identifiers to all driver core files · 989d42e8
      Greg Kroah-Hartman authored
      It's good to have SPDX identifiers in all files to make it easier to
      audit the kernel tree for correct licenses.
      Update the driver core files files with the correct SPDX license
      identifier based on the license text in the file itself.  The SPDX
      identifier is a legally binding shorthand, which can be used instead of
      the full boiler plate text.
      This work is based on a script and data from Thomas Gleixner, Philippe
      Ombredanne, and Kate Stewart.
      Cc: Johannes Berg <johannes@sipsolutions.net>
      Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>
      Cc: William Breathitt Gray <vilhelm.gray@gmail.com>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Kate Stewart <kstewart@linuxfoundation.org>
      Cc: Philippe Ombredanne <pombredanne@nexb.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  2. 31 Oct, 2011 1 commit
  3. 20 Apr, 2008 1 commit
  4. 07 Apr, 2008 1 commit
    • James Bottomley's avatar
      [SCSI] transport_class: BUG if we can't release the attribute container · 2f3edc69
      James Bottomley authored
      Every current transport class calls transport_container_release but
      ignores the return value.  This is catastrophic if it returns an error
      because the containers are part of a global list and the next action of
      almost every transport class is to free the memory used by the
      Fix this by making transport_container_release a void, but making it BUG
      if attribute_container_release returns an error ... this catches the
      root cause of a system panic much earlier.  If we don't do this, we get
      an eventual BUG when the attribute container list notices the corruption
      caused by the freed memory it's still referencing.
      Also made attribute_container_release __must_check as a reminder.
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
  5. 03 Mar, 2008 1 commit
  6. 28 Aug, 2005 1 commit
  7. 14 Aug, 2005 1 commit
    • James Bottomley's avatar
      [SCSI] correct transport class abstraction to work outside SCSI · d0a7e574
      James Bottomley authored
      I recently tried to construct a totally generic transport class and
      found there were certain features missing from the current abstract
      transport class.  Most notable is that you have to hang the data on the
      class_device but most of the API is framed in terms of the generic
      device, not the class_device.
      These changes are two fold
      - Provide the class_device to all of the setup and configure APIs
      - Provide and extra API to take the device and the attribute class and
        return the corresponding class_device
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
  8. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      Let it rip!