1. 02 Oct, 2006 2 commits
    • Serge E. Hallyn's avatar
      [PATCH] namespaces: utsname: use init_utsname when appropriate · 96b644bd
      Serge E. Hallyn authored
      
      
      In some places, particularly drivers and __init code, the init utsns is the
      appropriate one to use.  This patch replaces those with a the init_utsname
      helper.
      
      Changes: Removed several uses of init_utsname().  Hope I picked all the
      	right ones in net/ipv4/ipconfig.c.  These are now changed to
      	utsname() (the per-process namespace utsname) in the previous
      	patch (2/7)
      
      [akpm@osdl.org: CIFS fix]
      Signed-off-by: default avatarSerge E. Hallyn <serue@us.ibm.com>
      Cc: Kirill Korotaev <dev@openvz.org>
      Cc: "Eric W. Biederman" <ebiederm@xmission.com>
      Cc: Herbert Poetzl <herbert@13thfloor.at>
      Cc: Andrey Savochkin <saw@sw.ru>
      Cc: Serge Hallyn <serue@us.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      96b644bd
    • Jeff Dike's avatar
      [PATCH] const struct tty_operations · b68e31d0
      Jeff Dike authored
      
      
      As part of an SMP cleanliness pass over UML, I consted a bunch of
      structures in order to not have to document their locking.  One of these
      structures was a struct tty_operations.  In order to const it in UML
      without introducing compiler complaints, the declaration of
      tty_set_operations needs to be changed, and then all of its callers need to
      be fixed.
      
      This patch declares all struct tty_operations in the tree as const.  In all
      cases, they are static and used only as input to tty_set_operations.  As an
      extra check, I ran an i386 allyesconfig build which produced no extra
      warnings.
      
      53 drivers are affected.  I checked the history of a bunch of them, and in
      most cases, there have been only a handful of maintenance changes in the
      last six months.  serial_core.c was the busiest one that I looked at.
      Signed-off-by: default avatarJeff Dike <jdike@addtoit.com>
      Acked-by: default avatarAlan Cox <alan@redhat.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      b68e31d0
  2. 01 Oct, 2006 2 commits
  3. 28 Sep, 2006 4 commits
  4. 27 Sep, 2006 19 commits
  5. 31 Aug, 2006 1 commit
  6. 02 Aug, 2006 3 commits
  7. 12 Jul, 2006 1 commit
    • David Brownell's avatar
      [PATCH] USB: gadget section fixups · a353678d
      David Brownell authored
      
      
      Recent section changes broke gadget builds on some platforms.  This patch
      is the best fix that's available until better section markings exist:
      
       - There's a lot of cleanup code that gets used in both init and exit paths;
         stop marking it as "__exit".
      
         (Best fix for this would be an "__init_or_exit" section marking, putting
         the cleanup in __init when __exit sections get discarded else in __exit.)
      
       - Stop marking the use-once probe routines as "__init" since references
         to those routines are not allowed from driver structures.  They're now
         marked "__devinit", which in practice is a net lose.
      
         (Best fix for this is likely to separate such use-once probe routines
         from the driver structure ... but in general, all busses that aren't
         hotpluggable will be forced to waste memory for all probe-only code.)
      
      In general these broken section rules waste an average of two to four kBytes
      per driver of code bloat ... because none of the relevant code can ever be
      reused after module initialization.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      a353678d
  8. 03 Jul, 2006 1 commit
  9. 02 Jul, 2006 1 commit
  10. 30 Jun, 2006 1 commit
  11. 29 Jun, 2006 1 commit
  12. 26 Jun, 2006 3 commits
  13. 23 Jun, 2006 1 commit
    • Jens Axboe's avatar
      [PATCH] Kill PF_SYNCWRITE flag · b31dc66a
      Jens Axboe authored
      
      
      A process flag to indicate whether we are doing sync io is incredibly
      ugly. It also causes performance problems when one does a lot of async
      io and then proceeds to sync it. Part of the io will go out as async,
      and the other part as sync. This causes a disconnect between the
      previously submitted io and the synced io. For io schedulers such as CFQ,
      this will cause us lost merges and suboptimal behaviour in scheduling.
      
      Remove PF_SYNCWRITE completely from the fsync/msync paths, and let
      the O_DIRECT path just directly indicate that the writes are sync
      by using WRITE_SYNC instead.
      Signed-off-by: default avatarJens Axboe <axboe@suse.de>
      b31dc66a