1. 10 11月, 2007 15 次提交
  2. 09 11月, 2007 2 次提交
  3. 08 11月, 2007 3 次提交
  4. 07 11月, 2007 12 次提交
    • A
      [TTY]: Use tty_mode_ioctl() in network drivers. · d0127539
      Alan Cox 提交于
      We conciously make a change here - we permit mode and speed setting to
      be done in things like SLIP mode. There isn't actually a technical
      reason to disallow this. It's usually a silly thing to do but we can
      do it and soemone might wish to do so.
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d0127539
    • A
      [TTY]: Fix network driver interactions with TCGET/SET calls. · 0fc00e24
      Alan Cox 提交于
      Dave Miller noted various cases where line disciplines for things like
      ppp go poking around in termios themselves in ways that broke with the
      new termios code. Rather than have them all learning about termios
      internals provide proper methods for this
      
      - tty_mode_ioctl()
      
      	This handles all the terminal mode handling for speed/carrier
      etc and none of the methods are ldisc dependant so they can be called
      by any user
      
      - tty_perform_flush()
      
      	This extracts the flush functionality and enables pppd the ppp
      layer to share it cleanly.
      
      The existing n_tty_ioctl code is refactored in this patch to provide
      the new functions and to call them itself appropriately. This patch
      has no (intended) behaviour changes and simply prepares for the other
      fixes.
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      0fc00e24
    • A
      [NET]: Let USB_USBNET always select MII. · 4aa92cd9
      Adrian Bunk 提交于
      All this USB_USBNET_MII trickery is simply not worth it considering how
      few code it saves.
      
      As a side effect, this also fixes the following compile error reported
      by Toralf Frster:
      
      <--  snip  -->
      
      ...
        LD      .tmp_vmlinux1
      drivers/built-in.o: In function `usbnet_set_settings':
      (.text+0xf1876): undefined reference to `mii_ethtool_sset'
      drivers/built-in.o: In function `usbnet_get_settings':
      (.text+0xf1836): undefined reference to `mii_ethtool_gset'
      drivers/built-in.o: In function `usbnet_get_link':
      (.text+0xf18d6): undefined reference to `mii_link_ok'
      drivers/built-in.o: In function `usbnet_nway_reset':
      (.text+0xf18f6): undefined reference to `mii_nway_restart'
      make: *** [.tmp_vmlinux1] Error 1
      
      <--  snip  -->
      Signed-off-by: NAdrian Bunk <bunk@kernel.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4aa92cd9
    • D
      [RRUNNER]: Do not muck with sysctl_{r,w}mem_max · df1e6e54
      David S. Miller 提交于
      Drivers have no business changing these values.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      df1e6e54
    • R
      [VETH]: Clarify "virtual ethernet device" to "virtual ethernet pair device". · 6a9a0250
      Rusty Russell 提交于
      It'd also be nice to mention "containers" somewhere in the help text
      (I'm assuming that's what it's for?).
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6a9a0250
    • J
      [PPP]: L2TP: Fix oops in transmit and receive paths · 91781004
      James Chapman 提交于
      Changes made on 18-sep to fix skb handling in the pppol2tp driver
      broke the transmit and receive paths. Users are only running into this
      now because distros are now using 2.6.23 and I must have messed up
      when I tested the change.
      
      For receive, we now do our own calculation of how much to pull from
      the skb (variable length L2TP header) rather than using
      skb_transport_offset(). Also, if the skb isn't a data packet, it must
      be passed back to UDP with skb->data pointing to the UDP header.
      
      For transmit, make sure skb->sk is set up because ip_queue_xmit()
      needs it.
      Signed-off-by: NJames Chapman <jchapman@katalix.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      91781004
    • P
      rtc: rtc-sh: Zero out tm value for invalid rtc states. · 0ac554b9
      Paul Mundt 提交于
      Follows the changes of some of the other RTC drivers. If the tm
      value is bogus, just zero it out. Adds some sanity for RTC_RD_TIME.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      0ac554b9
    • P
      rtc: sh-rtc: Handle rtc_device_register() failure properly. · 29dd0dae
      Paul Mundt 提交于
      Currently if rtc_device_register() fails we have an IS_ERR() on
      the wrong pointer, which causes this to always be skipped. Fix
      this up to actually check the right pointer. The return value
      was always correct, even though the check was wrong.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      29dd0dae
    • N
      sh: Remove SCI_NPORTS from sh-sci.h · 694caef5
      Nobuhiro Iwamatsu 提交于
      When SH7710 and SH7712 are used, SCI_NPORTS redefined.
      Remove it.
      Signed-off-by: NNobuhiro Iwamatsu <iwamatsu@nigauri.org>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      694caef5
    • P
      sh: Kill off the remaining ST40 cruft. · f9669187
      Paul Mundt 提交于
      The ST40 stuff in-tree hasn't built for some time, and hasn't been
      updated for over 3 years. ST maintains their own out-of-tree changes
      and rebases occasionally, and that's ultimately where all of the ST40
      users go anyways.
      
      In order for the ST40 code to be brought up to date most of the stuff
      removed in this changeset would have to be rewritten anyways, so there's
      very little benefit in keeping the remnants around either.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      f9669187
    • P
      superhyway: Handle device_register() retval properly. · 07782cec
      Paul Mundt 提交于
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      07782cec
    • S
      firewire: fw-sbp2: fix refcounting · 7c45d191
      Stefan Richter 提交于
      Since patch "fw-sbp2: use an own workqueue (fix system responsiveness)"
      increased parallelism between fw-sbp2 and fw-core, it was possible that
      fw-sbp2 didn't release the SCSI device when the FireWire device was
      disconnected.
      
      This happened if sbp2_update() ran during sbp2_login(), because a bus
      reset occurred during sbp2_login().  The sbp2_login() work would [try
      to] reschedule itself because it failed due to the bus reset, and it
      would _not_ drop its reference on the target.  However, sbp2_update()
      would schedule sbp2_login() too before sbp2_login() rescheduled itself
      and hence sbp2_update() would take an additional reference.  And then
      we would have one reference too many.
      
      The fix is to _always_ drop the reference when leaving the sbp2_login()
      work.  If the sbp2_login() work reschedules itself, it takes a
      reference, but only if it wasn't already rescheduled by sbp2_update().
      
      Ditto in the sbp2_reconnect() work.
      
      The resulting code is actually simpler than before:  We _always_ take
      a reference when successfully scheduling work.  And we _always_ drop
      a reference when leaving a workqueue job.  No exceptions.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      7c45d191
  5. 06 11月, 2007 8 次提交