1. 08 Aug, 2014 1 commit
  2. 15 Nov, 2013 1 commit
  3. 28 Feb, 2013 2 commits
  4. 11 Apr, 2012 1 commit
  5. 31 Oct, 2011 1 commit
    • Paul Gortmaker's avatar
      kernel: Map most files to use export.h instead of module.h · 9984de1a
      Paul Gortmaker authored
      The changed files were only including linux/module.h for the
      EXPORT_SYMBOL infrastructure, and nothing else.  Revector them
      onto the isolated export header for faster compile times.
      Nothing to see here but a whole lot of instances of:
        -#include <linux/module.h>
        +#include <linux/export.h>
      This commit is only changing the kernel dir; next targets
      will probably be mm, fs, the arch dirs, etc.
      Signed-off-by: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
  6. 01 Oct, 2010 1 commit
    • Ira W. Snyder's avatar
      kfifo: fix scatterlist usage · 399f1e30
      Ira W. Snyder authored
      The kfifo_dma family of functions use sg_mark_end() on the last element in
      their scatterlist.  This forces use of a fresh scatterlist for each DMA
      operation, which makes recycling a single scatterlist impossible.
      Change the behavior of the kfifo_dma functions to match the usage of the
      dma_map_sg function.  This means that users must respect the returned
      nents value.  The sample code is updated to reflect the change.
      This bug is trivial to cause: call kfifo_dma_in_prepare() such that it
      prepares a scatterlist with a single entry comprising the whole fifo.
      This is the case when you map the entirety of a newly created empty fifo.
      This causes the setup_sgl() function to mark the first scatterlist entry
      as the end of the chain, no matter what comes after it.
      Afterwards, add and remove some data from the fifo such that another call
      to kfifo_dma_in_prepare() will create two scatterlist entries.  It returns
      nents=2.  However, due to the previous sg_mark_end() call, sg_is_last()
      will now return true for the first scatterlist element.  This causes the
      sample code to print a single scatterlist element when it should print
      By removing the call to sg_mark_end(), we make the API as similar as
      possible to the DMA mapping API.  All users are required to respect the
      returned nents.
      Signed-off-by: default avatarIra W. Snyder <iws@ovro.caltech.edu>
      Cc: Stefani Seibold <stefani@seibold.net>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  7. 20 Aug, 2010 1 commit
  8. 12 Aug, 2010 1 commit
  9. 11 Aug, 2010 1 commit
  10. 16 Feb, 2010 2 commits
  11. 03 Feb, 2010 1 commit
  12. 16 Jan, 2010 4 commits
  13. 22 Dec, 2009 6 commits
  14. 19 Sep, 2009 1 commit
  15. 17 Jun, 2009 1 commit
  16. 16 Jul, 2007 1 commit
  17. 11 Feb, 2007 1 commit
  18. 29 Sep, 2006 1 commit
    • Paul E. McKenney's avatar
      [PATCH] memory ordering in __kfifo primitives · a45bce49
      Paul E. McKenney authored
      Both __kfifo_put() and __kfifo_get() have header comments stating that if
      there is but one concurrent reader and one concurrent writer, locking is not
      necessary.  This is almost the case, but a couple of memory barriers are
      needed.  Another option would be to change the header comments to remove the
      bit about locking not being needed, and to change the those callers who
      currently don't use locking to add the required locking.  The attachment
      analyzes this approach, but the patch below seems simpler.
      Signed-off-by: default avatarPaul E. McKenney <paulmck@us.ibm.com>
      Cc: Stelian Pop <stelian@popies.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  19. 08 Oct, 2005 1 commit
  20. 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!