)]}'
{
  "log": [
    {
      "commit": "251eb40f5ccd07a905633a816fbf8f2b6b25cced",
      "tree": "6e5c1579acbdfb240745e4b9b3f6e999681ce4d8",
      "parents": [
        "133bb070e94ab41d750c6f2160c8843e46f11b78"
      ],
      "author": {
        "name": "Jonathan Cameron",
        "email": "jic23@cam.ac.uk",
        "time": "Mon Apr 13 14:39:45 2009 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Mon Apr 13 15:04:29 2009 -0700"
      },
      "message": "hwmon: sht15 humidity sensor driver\n\nData sheet at:\nhttp://www.sensirion.ch/en/pdf/product_information/Datasheet-humidity-sensor-SHT1x.pdf\n\nThese sensors communicate over a 2 wire bus running a device specific\nprotocol.  The complexity of the driver is mainly due to handling the\nsubstantial delays between requesting a reading and the device pulling the\ndata line low to indicate that the data is available.  This is handled by\nan interrupt that is disabled under all other conditions.\n\nI wasn\u0027t terribly clear on the best way to handle this, so comments on\nthat aspect would be particularly welcome!\n\nInterpretation of the temperature depends on knowing the supply voltage.\nIf configured in a board config as a regulator consumer this is obtained\nfrom the regulator subsystem.  If not it should be provided in the\nplatform data.\n\nI\u0027ve placed this driver in the hwmon subsystem as it is definitely a\ndevice that may be used for hardware monitoring and with it\u0027s relatively\nslow response times (up to 120 millisecs to get a reading) a caching\nstrategy certainly seems to make sense!\n\nSigned-off-by: Jonathan Cameron \u003cjic23@cam.ac.uk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n"
    }
  ]
}