1. 14 9月, 2006 1 次提交
  2. 12 9月, 2006 1 次提交
    • A
      [PATCH] Remove more unnecessary driver printk's · d5b20697
      Andy Gospodarek 提交于
      As I promised last week, here is the first pass at removing all
      unnecessary printk's that exist in network device drivers currently in
      promiscuous mode.  The duplicate messages are not needed so they have
      been removed.  Some of these drivers are quite old and might not need an
      update, but I did them all anyway.
      
      I am currently auditing the remaining conditional printk's and will send
      out a patch for those soon.
      Signed-off-by: NAndy Gospodarek <andy@greyhouse.net>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      d5b20697
  3. 20 8月, 2006 2 次提交
  4. 09 8月, 2006 1 次提交
  5. 06 7月, 2006 2 次提交
    • J
      [netdrvr] minor cleanups in Becker-derived drivers · 46009c8b
      Jeff Garzik 提交于
      - fealnx: convert #define to enum
      - fealnx, sundance: mark chip info table __devinitdata
      - fealnx: use dev_printk() during probe
      - fealnx: formatting cleanups
      - starfire: remove obsolete comment
      - sundance, via-rhine: add some whitespace where useful, in tables
      - sundance: prefer "{ }" table terminator
      - via-rhine: mark PCI probe table const
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      46009c8b
    • J
      [netdrvr] Remove Linux-specific changelogs from several Becker template drivers · 03a8c661
      Jeff Garzik 提交于
      When in-kernel net drivers branched from Donald Becker's vanilla driver
      set, in the days before BitKeeper and git, a driver changelog was
      maintained in the driver source code.  These days, the kernel's
      changelog is far superior and much more accurate, so the in-driver
      changelogs are removed.
      
      Another relic of the Becker/kernel split was version numbering, using
      "foo-LKx.y.z" notation, resulting in weird version numbers like
      "1.17b-LK1.1.9".  These drivers are for older hardware, and see few
      changes these days, so the version numbers were all bumped to something
      more simple.
      
      Finally, in xircom_tulip_cb specifically, an additional cleanup removes
      the always-enabled CARDBUS cpp macro.
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      03a8c661
  6. 03 7月, 2006 1 次提交
  7. 16 6月, 2006 1 次提交
  8. 04 3月, 2006 1 次提交
  9. 27 1月, 2006 1 次提交
  10. 29 10月, 2005 1 次提交
  11. 20 10月, 2005 1 次提交
  12. 19 10月, 2005 2 次提交
  13. 14 9月, 2005 1 次提交
  14. 29 6月, 2005 1 次提交
    • D
      [NET]: Remove gratuitous use of skb->tail in network drivers. · 689be439
      David S. Miller 提交于
      Many drivers use skb->tail unnecessarily.
      
      In these situations, the code roughly looks like:
      
      	dev = dev_alloc_skb(...);
      
      	[optional] skb_reserve(skb, ...);
      
      	... skb->tail ...
      
      But even if the skb_reserve() happens, skb->data equals
      skb->tail.  So it doesn't make any sense to use anything
      other than skb->data in these cases.
      
      Another case was the s2io.c driver directly mucking with
      the skb->data and skb->tail pointers.  It really just wanted
      to do an skb_reserve(), so that's what the code was changed
      to do instead.
      
      Another reason I'm making this change as it allows some SKB
      cleanups I have planned simpler to merge.  In those cleanups,
      skb->head, skb->tail, and skb->end pointers are removed, and
      replaced with skb->head_room and skb->tail_room integers.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      Acked-by: NJeff Garzik <jgarzik@pobox.com>
      689be439
  15. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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