1. 23 9月, 2011 1 次提交
    • J
      TTY: serial, move 68360 driver to staging · 3a0db721
      Jiri Slaby 提交于
      This driver has been broken at least since 2008. At that time,
      a88487c7 (Fix compile errors in SGI console drivers) broke this
      driver completely.
      
      And since nobody noticed for the past 3 years, move it into staging. I
      think this will rot there and we will throw it away completely after
      some time. Or maybe someone will volunteer to fix it ;).
      Signed-off-by: NJiri Slaby <jslaby@suse.cz>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Cc: Alan Cox <alan@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      3a0db721
  2. 16 8月, 2011 1 次提交
    • A
      gma500: kill MIPI interface types · c3585aa9
      Alan Cox 提交于
      Kirill Shutemov found problems with the non-upstream IMG driver where the
      use of extra DRM encoder/connector types caused random crashes when the DRM
      layer tried to display their matching name. This removes the MIPI types
      matching the changes Pauli Nieminen made to the non upstream driver set.
      
      As Pauli points out:
      " MIPI (or DSI) is protocol specification on top of LVDS serial bus. That
       makes it resonable to call MIPI connectors and encoders LVDS."
      
      (and indeed they may also be HDMI convertors or similar when we want to
       report a more useful to end user result)
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      c3585aa9
  3. 09 8月, 2011 4 次提交
  4. 03 8月, 2011 16 次提交
  5. 28 7月, 2011 9 次提交
  6. 27 7月, 2011 2 次提交
  7. 25 7月, 2011 1 次提交
  8. 24 7月, 2011 1 次提交
  9. 22 7月, 2011 1 次提交
  10. 21 7月, 2011 1 次提交
    • J
      fs: push i_mutex and filemap_write_and_wait down into ->fsync() handlers · 02c24a82
      Josef Bacik 提交于
      Btrfs needs to be able to control how filemap_write_and_wait_range() is called
      in fsync to make it less of a painful operation, so push down taking i_mutex and
      the calling of filemap_write_and_wait() down into the ->fsync() handlers.  Some
      file systems can drop taking the i_mutex altogether it seems, like ext3 and
      ocfs2.  For correctness sake I just pushed everything down in all cases to make
      sure that we keep the current behavior the same for everybody, and then each
      individual fs maintainer can make up their mind about what to do from there.
      Thanks,
      Acked-by: NJan Kara <jack@suse.cz>
      Signed-off-by: NJosef Bacik <josef@redhat.com>
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      02c24a82
  11. 20 7月, 2011 2 次提交
  12. 19 7月, 2011 1 次提交