Skip to content
Snippets Groups Projects
  1. Sep 25, 2018
  2. Aug 25, 2018
    • Jens Axboe's avatar
      libata: maintainership update · 7634ccd2
      Jens Axboe authored
      
      Tejun Heo wrote:
      >
      > I asked Jens whether he could take care of the libata tree and he
      > thankfully agreed, so, from now on, Jens will be the libata
      > maintainer.
      >
      > Thanks a lot!
      
      Thanks for your work in this area. I still remember the first linux
      storage summit we did in Vancouver 2001, Tejun was invited to talk about
      his libata error handling work. Before that, it was basically a crap
      shoot if we recovered properly or not... A lot of water has flown under
      the bridge since then!
      
      Here's an "official" patch. Linus, can you apply it?
      
      Signed-off-by: default avatarJens Axboe <axboe@kernel.dk>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      7634ccd2
  3. Aug 24, 2018
  4. Aug 17, 2018
  5. Aug 16, 2018
  6. Aug 14, 2018
  7. Aug 11, 2018
  8. Aug 09, 2018
    • Hans de Goede's avatar
      platform/x86: Add ACPI i2c-multi-instantiate pseudo driver · e64e8498
      Hans de Goede authored
      
      On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node
      per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1
      i2c-device.
      
      But in some rare cases the manufacturer has decided to describe multiple
      i2c-devices in a single ACPI fwnode with multiple I2cSerialBus resources.
      
      An earlier attempt to fix this in the i2c-core resulted in a lot of extra
      code to support this corner-case.
      
      This commit introduces a new i2c-multi-instantiate driver which fixes this
      in a different way. This new driver can be built as a module which will
      only loaded on affected systems.
      
      This driver will instantiate a new i2c-client per I2cSerialBus resource,
      using the driver_data from the acpi_device_id it is binding to to tell it
      which chip-type (and optional irq-resource) to use when instantiating.
      
      Note this driver depends on a platform device being instantiated for the
      ACPI fwnode, see the i2c_multi_instantiate_ids list of ACPI device-ids in
      drivers/acpi/scan.c: acpi_device_enumeration_by_parent().
      
      Acked-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Acked-by: default avatarWolfram Sang <wsa@the-dreams.de>
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      e64e8498
  9. Aug 08, 2018
  10. Aug 07, 2018
  11. Aug 02, 2018
  12. Aug 01, 2018
  13. Jul 31, 2018
  14. Jul 30, 2018
  15. Jul 27, 2018
  16. Jul 26, 2018
  17. Jul 25, 2018
  18. Jul 24, 2018
  19. Jul 23, 2018
  20. Jul 21, 2018
  21. Jul 20, 2018
Loading