1. 24 Mar, 2009 1 commit
  2. 10 Dec, 2008 1 commit
    • Adrian Hunter's avatar
      [MTD] update internal API to support 64-bit device size · 69423d99
      Adrian Hunter authored
      MTD internal API presently uses 32-bit values to represent
      device size.  This patch updates them to 64-bits but leaves
      the external API unchanged.  Extending the external API
      is a separate issue for several reasons.  First, no one
      needs it at the moment.  Secondly, whether the implementation
      is done with IOCTLs, sysfs or both is still debated.  Thirdly
      external API changes require the internal API to be accepted
      first.
      
      Note that although the MTD API will be able to support 64-bit
      device sizes, existing drivers do not and are not required
      to do so, although NAND base has been updated.
      
      In general, changing from 32-bit to 64-bit values cause little
      or no changes to the majority of the code with the following
      exceptions:
          	- printk message formats
          	- division and modulus of 64-bit values
          	- NAND base support
      	- 32-bit local variables used by mtdpart and mtdconcat
      	- naughtily assuming one structure maps to another
      	in MEMERASE ioctl
      Signed-off-by: default avatarAdrian Hunter <ext-adrian.hunter@nokia.com>
      Signed-off-by: default avatarArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      Signed-off-by: default avatarDavid Woodhouse <David.Woodhouse@intel.com>
      69423d99
  3. 04 Jun, 2008 4 commits
  4. 03 Feb, 2008 1 commit
  5. 28 Jun, 2007 1 commit
  6. 14 Feb, 2007 1 commit
    • Tim Schmielau's avatar
      [PATCH] remove many unneeded #includes of sched.h · cd354f1a
      Tim Schmielau authored
      After Al Viro (finally) succeeded in removing the sched.h #include in module.h
      recently, it makes sense again to remove other superfluous sched.h includes.
      There are quite a lot of files which include it but don't actually need
      anything defined in there.  Presumably these includes were once needed for
      macros that used to live in sched.h, but moved to other header files in the
      course of cleaning it up.
      
      To ease the pain, this time I did not fiddle with any header files and only
      removed #includes from .c-files, which tend to cause less trouble.
      
      Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
      arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
      allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
      configs in arch/arm/configs on arm.  I also checked that no new warnings were
      introduced by the patch (actually, some warnings are removed that were emitted
      by unnecessarily included header files).
      Signed-off-by: default avatarTim Schmielau <tim@physik3.uni-rostock.de>
      Acked-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      cd354f1a
  7. 29 Nov, 2006 4 commits
    • David Woodhouse's avatar
      [MTD] Use EXPORT_SYMBOL_GPL() for exported symbols. · dd36f267
      David Woodhouse authored
      While we're fixing up the newly-added symbol, change the neighbouring ones
      too, for consistency and also to reflect the author's interpretation of
      the GPL -- which is that _no_ non-GPL modules are permitted. The author
      always intended his code to be released under the GPL, and believes that
      any new interpretation of 'EXPORT_SYMBOL' as being any different from
      'EXPORT_SYMBOL_GPL' is entirely invalid; the GPL requires that _all_
      exports have the semantics of the new 'EXPORT_SYMBOL_GPL', which means the
      extra four characters are entirely redundant.
      
      But since those four extra characters trigger the check for illegal
      modules in a way that just EXPORT_SYMBOL does not, it's useful to change
      anyway. This action in no way indicates an admission that there is any
      legal distinction between the two states, and in particular does not
      indicate that the author believes that non-GPL modules may use symbols
      exported with EXPORT_SYMBOL alone.
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      dd36f267
    • Artem Bityutskiy's avatar
      [MTD] return error code from get_mtd_device() · 9c74034f
      Artem Bityutskiy authored
      get_mtd_device() returns NULL in case of any failure. Teach it to return an
      error code instead. Fix all users as well.
      Signed-off-by: default avatarArtem Bityutskiy <dedekind@infradead.org>
      9c74034f
    • Artem Bityutskiy's avatar
      [MTD] add get and put methods · 9fe912ce
      Artem Bityutskiy authored
      This patch adds get_device() and put_device() methods to the MTD description
      structure (struct mtd_info). These methods are called by MTD whenever the MTD
      device is get or put. They are needed when the underlying driver is something
      smarter then just flash chip driver, for example UBI.
      Signed-off-by: default avatarArtem Bityutskiy <dedekind@infradead.org>
      9fe912ce
    • Artem Bityutskiy's avatar
      [MTD] add get_mtd_device_nm() function · 7799308f
      Artem Bityutskiy authored
      This patch adds one more function to the MTD interface to make it possible to
      open MTD devices by their names, not only numbers. This is very handy in many
      situations. Also, MTD device number depend on load order and may vary, while
      names are fixed.
      Signed-off-by: default avatarArtem Bityutskiy <dedekind@infradead.org>
      7799308f
  8. 22 Sep, 2006 1 commit
  9. 30 Jun, 2006 1 commit
  10. 14 Jun, 2006 1 commit
  11. 25 May, 2006 1 commit
  12. 31 Mar, 2006 2 commits
  13. 07 Nov, 2005 1 commit
  14. 06 Nov, 2005 1 commit
  15. 23 May, 2005 1 commit
  16. 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!
      1da177e4