An error occurred fetching the project authors.
  1. 21 Nov, 2008 1 commit
    • John W. Linville's avatar
      netdevice zd1201: Convert directly reference of netdev->priv to netdev_priv() · 3d29b0c3
      John W. Linville authored
      We have some reasons to kill netdev->priv:
      1. netdev->priv is equal to netdev_priv().
      2. netdev_priv() wraps the calculation of netdev->priv's offset, obviously
         netdev_priv() is more flexible than netdev->priv.
      But we cann't kill netdev->priv, because so many drivers reference to it
      directly.
      
      OK, becasue Dave S. Miller said, "every direct netdev->priv usage is a bug",
      and I want to kill netdev->priv later, I decided to convert all the direct
      reference of netdev->priv first.
      
      (Original patch posted by Wang Chen <wangchen@cn.fujitsu.com> w/ above
      changelog but using dev->ml_priv.  That doesn't seem appropriate
      to me for this driver, so I've revamped it to use netdev_priv()
      instead. -- JWL)
      Reviewed-by: default avatarWang Chen <wangchen@cn.fujitsu.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      3d29b0c3
  2. 10 Nov, 2008 1 commit
  3. 04 Nov, 2008 1 commit
  4. 10 Jul, 2008 1 commit
  5. 17 Jun, 2008 1 commit
    • David S. Miller's avatar
      wext: Emit event stream entries correctly when compat. · ccc58057
      David S. Miller authored
      Three major portions to this change:
      
      1) Add IW_EV_COMPAT_LCP_LEN, IW_EV_COMPAT_POINT_OFF,
         and IW_EV_COMPAT_POINT_LEN helper defines.
      
      2) Delete iw_stream_check_add_*(), they are unused.
      
      3) Add iw_request_info argument to iwe_stream_add_*(), and use it to
         size the event and pointer lengths correctly depending upon whether
         IW_REQUEST_FLAG_COMPAT is set or not.
      
      4) The mechanical transformations to the drivers and wireless stack
         bits to get the iw_request_info passed down into the routines
         modified in #3.  Also, explicit references to IW_EV_LCP_LEN are
         replaced with iwe_stream_lcp_len(info).
      
      With a lot of help and bug fixes from Masakazu Mokuno.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      ccc58057
  6. 18 Oct, 2007 1 commit
  7. 26 Apr, 2007 2 commits
  8. 01 Dec, 2006 1 commit
  9. 17 Oct, 2006 1 commit
  10. 05 Oct, 2006 1 commit
    • David Howells's avatar
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells authored
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: default avatarDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  11. 27 Sep, 2006 1 commit
    • Pete Zaitcev's avatar
      USB: Dealias -110 code (more complete) · 38e2bfc9
      Pete Zaitcev authored
      The purpose of this patch is to split off the case when a device does
      not reply on the lower level (which is reported by HC hardware), and
      a case when the device accepted the request, but does not reply at
      upper level. This redefinition allows to diagnose issues easier,
      without asking the user if the -110 happened "immediately".
      
      The usbmon splits such cases already thanks to its timestamp, but
      it's not always available.
      
      I adjusted all drivers which I found affected (by searching for "urb").
      Out of tree drivers may suffer a little bit, but I do not expect much
      breakage. At worst they may print a few messages.
      Signed-off-by: default avatarPete Zaitcev <zaitcev@redhat.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      38e2bfc9
  12. 25 Sep, 2006 1 commit
  13. 27 Jul, 2006 1 commit
  14. 05 Jun, 2006 2 commits
  15. 27 Mar, 2006 1 commit
  16. 20 Mar, 2006 1 commit
  17. 04 Jan, 2006 3 commits
  18. 28 Oct, 2005 1 commit
  19. 08 Sep, 2005 1 commit
    • Alan Stern's avatar
      [PATCH] USB: URB_ASYNC_UNLINK flag removed from the kernel · b375a049
      Alan Stern authored
      29 July 2005, Cambridge, MA:
      
      This afternoon Alan Stern submitted a patch to remove the URB_ASYNC_UNLINK
      flag from the Linux kernel.  Mr. Stern explained, "This flag is a relic
      from an earlier, less-well-designed system.  For over a year it hasn't
      been used for anything other than printing warning messages."
      
      An anonymous spokesman for the Linux kernel development community
      commented, "This is exactly the sort of thing we see happening all the
      time.  As the kernel evolves, support for old techniques and old code can
      be jettisoned and replaced by newer, better approaches.  Proprietary
      operating systems do not have the freedom or flexibility to change so
      quickly."
      
      Mr. Stern, a staff member at Harvard University's Rowland Institute who
      works on Linux only as a hobby, noted that the patch (labelled as548) did
      not update two files, keyspan.c and option.c, in the USB drivers' "serial"
      subdirectory.  "Those files need more extensive changes," he remarked.
      "They examine the status field of several URBs at times when they're not
      supposed to.  That will need to be fixed before the URB_ASYNC_UNLINK flag
      is removed."
      
      Greg Kroah-Hartman, the kernel maintainer responsible for overseeing all
      of Linux's USB drivers, did not respond to our inquiries or return our
      calls.  His only comment was "Applied, thanks."
      Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      b375a049
  20. 23 Aug, 2005 1 commit
  21. 29 Jul, 2005 1 commit
  22. 27 Jun, 2005 2 commits
  23. 28 May, 2005 1 commit
  24. 04 May, 2005 1 commit
    • Steven Cole's avatar
      [PATCH] USB: Spelling fixes for drivers/usb. · 093cf723
      Steven Cole authored
      Here are some spelling corrections for drivers/usb.
      
      cancelation -> cancellation
      succesful -> successful
      cancelation -> cancellation
      decriptor -> descriptor
      Initalize -> Initialize
      wierd -> weird
      Protocoll -> Protocol
      occured -> occurred
      successfull -> successful
      Procesing -> Processing
      devide -> divide
      Isochronuous -> Isochronous
      noticable -> noticeable
      Basicly -> Basically
      transfering -> transferring
      intialize -> initialize
      Incomming -> Incoming
      additionnal -> additional
      asume -> assume
      Unfortunatly -> Unfortunately
      retreive -> retrieve
      tranceiver -> transceiver
      Compatiblity -> Compatibility
      Incorprated -> Incorporated
      existance -> existence
      Ununsual -> Unusual
      Signed-off-by: default avatarSteven Cole <elenstev@mesatop.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      093cf723
  25. 22 Apr, 2005 1 commit
  26. 19 Apr, 2005 1 commit
  27. 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