1. 10 1月, 2006 3 次提交
  2. 06 1月, 2006 4 次提交
  3. 13 12月, 2005 2 次提交
  4. 09 11月, 2005 3 次提交
  5. 10 9月, 2005 1 次提交
  6. 06 9月, 2005 3 次提交
  7. 28 7月, 2005 1 次提交
  8. 13 7月, 2005 1 次提交
  9. 24 6月, 2005 3 次提交
  10. 22 6月, 2005 1 次提交
    • J
      [PATCH] I2C: Kill address ranges in non-sensors i2c chip drivers · b3d5496e
      Jean Delvare 提交于
      Some months ago, you killed the address ranges mechanism from all
      sensors i2c chip drivers (both the module parameters and the in-code
      address lists). I think it was a very good move, as the ranges can
      easily be replaced by individual addresses, and this allowed for
      significant cleanups in the i2c core (let alone the impressive size
      shrink for all these drivers).
      
      Unfortunately you did not do the same for non-sensors i2c chip drivers.
      These need the address ranges even less, so we could get rid of the
      ranges here as well for another significant i2c core cleanup. Here comes
      a patch which does just that. Since the process is exactly the same as
      what you did for the other drivers set already, I did not split this one
      in parts.
      
      A documentation update is included.
      
      The change saves 308 bytes in the i2c core, and an average 1382 bytes
      for chip drivers which use I2C_CLIENT_INSMOD, 126 bytes for those which
      do not.
      
      This change is required if we want to merge the sensors and non-sensors
      i2c code (and we want to do this).
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      Index: gregkh-2.6/Documentation/i2c/writing-clients
      ===================================================================
      b3d5496e
  11. 01 5月, 2005 1 次提交
  12. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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!
      1da177e4