1. 28 9月, 2010 2 次提交
  2. 25 9月, 2010 1 次提交
    • P
      Staging: ti-st: remove st_get_plat_device · d3654cd2
      Pavan Savoy 提交于
      In order to support multiple ST platform devices, a new symbol
      'st_get_plat_device' earlier needed to be exported by the arch/XX/brd-XX.c
      file which intends to add the ST platform device.
      
      On removing this dependency, now inside ST driver maintain the array of
      ST platform devices that would be registered.
      As of now let id=0, as and when we end up having such platforms
      where mutliple ST devices can exist, id would come from
      protocol drivers (BT, FM and GPS) as to on which platform device
      they want to register to.
      Signed-off-by: NPavan Savoy <pavan_savoy@ti.com>
      Acked-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Cc: Anca Emanuel <anca.emanuel@gmail.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      d3654cd2
  3. 21 9月, 2010 2 次提交
  4. 04 9月, 2010 12 次提交
  5. 24 8月, 2010 16 次提交
  6. 18 8月, 2010 1 次提交
    • N
      fs: fs_struct rwlock to spinlock · 2a4419b5
      Nick Piggin 提交于
      fs: fs_struct rwlock to spinlock
      
      struct fs_struct.lock is an rwlock with the read-side used to protect root and
      pwd members while taking references to them. Taking a reference to a path
      typically requires just 2 atomic ops, so the critical section is very small.
      Parallel read-side operations would have cacheline contention on the lock, the
      dentry, and the vfsmount cachelines, so the rwlock is unlikely to ever give a
      real parallelism increase.
      
      Replace it with a spinlock to avoid one or two atomic operations in typical
      path lookup fastpath.
      Signed-off-by: NNick Piggin <npiggin@kernel.dk>
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      2a4419b5
  7. 11 8月, 2010 2 次提交
    • R
      param: remove unnecessary writable charp · dca41306
      Rusty Russell 提交于
      sysfs-writable charp arguments need to be locked against modification
      (since the old ones may be kfreed underneath us).  String arguments
      are much simpler, so use them for small strings (eg. IFNAMSIZ).
      
      lkdtm only uses the parameters at module initialization time, so there's
      not much point making them writable.
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      Reviewed-by: NTakashi Iwai <tiwai@suse.de>
      Tested-by: NPhil Carmody <ext-phil.2.carmody@nokia.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: M. Mohan Kumar <mohan@in.ibm.com>
      Cc: Greg Kroah-Hartman <gregkh@suse.de>
      Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
      Cc: Jeff Mahoney <jeffm@suse.com>
      Cc: Julia Lawall <julia@diku.dk>
      Cc: devel@driverdev.osuosl.org
      dca41306
    • A
      USB: convert usb_hcd bitfields into atomic flags · 541c7d43
      Alan Stern 提交于
      This patch (as1393) converts several of the single-bit fields in
      struct usb_hcd to atomic flags.  This is for safety's sake; not all
      CPUs can update bitfield values atomically, and these flags are used
      in multiple contexts.
      
      The flag fields that are set only during registration or removal can
      remain as they are, since non-atomic accesses at those times will not
      cause any problems.
      
      (Strictly speaking, the authorized_default flag should become atomic
      as well.  I didn't bother with it because it gets changed only via
      sysfs.  It can be done later, if anyone wants.)
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      541c7d43
  8. 10 8月, 2010 2 次提交
    • A
      Make ->drop_inode() just return whether inode needs to be dropped · 45321ac5
      Al Viro 提交于
      ... and let iput_final() do the actual eviction or retention
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      45321ac5
    • C
      remove inode_setattr · 1025774c
      Christoph Hellwig 提交于
      Replace inode_setattr with opencoded variants of it in all callers.  This
      moves the remaining call to vmtruncate into the filesystem methods where it
      can be replaced with the proper truncate sequence.
      
      In a few cases it was obvious that we would never end up calling vmtruncate
      so it was left out in the opencoded variant:
      
       spufs: explicitly checks for ATTR_SIZE earlier
       btrfs,hugetlbfs,logfs,dlmfs: explicitly clears ATTR_SIZE earlier
       ufs: contains an opencoded simple_seattr + truncate that sets the filesize just above
      
      In addition to that ncpfs called inode_setattr with handcrafted iattrs,
      which allowed to trim down the opencoded variant.
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      1025774c
  9. 09 8月, 2010 2 次提交
新手
引导
客服 返回
顶部