1. 11 10月, 2007 2 次提交
    • R
      [NET]: Nuke SET_MODULE_OWNER macro. · 10d024c1
      Ralf Baechle 提交于
      It's been a useless no-op for long enough in 2.6 so I figured it's time to
      remove it.  The number of people that could object because they're
      maintaining unified 2.4 and 2.6 drivers is probably rather small.
      
      [ Handled drivers added by netdev tree and some missed IRDA cases... -DaveM ]
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      10d024c1
    • Y
      dev->priv to netdev_priv(dev), drivers/net/tokenring/ · eda10531
      Yoann Padioleau 提交于
      Replacing accesses to dev->priv to netdev_priv(dev). The replacment
      is safe when netdev_priv is used to access a private structure that is
      right next to the net_device structure in memory.
      Cf http://groups.google.com/group/comp.os.linux.development.system/browse_thread/thread/de19321bcd94dbb8/0d74a4adcd6177bd
      This is the case when the net_device structure was allocated with
      a call to alloc_netdev or one of its derivative.
      
      Here is an excerpt of the semantic patch that performs the transformation
      
      @ rule1 @
      type T;
      struct net_device *dev;
      @@
      
       dev =
      (
              alloc_netdev
      |
              alloc_etherdev
      |
              alloc_trdev
      )
         (sizeof(T), ...)
      
      @ rule1bis @
      struct net_device *dev;
      expression E;
      @@
       dev->priv = E
      
      @ rule2 depends on rule1 && !rule1bis  @
      struct net_device *dev;
      type rule1.T;
      @@
      
      - (T*) dev->priv
      + netdev_priv(dev)
      
      PS: I have performed the same transformation on the whole kernel
      and it affects around 70 files, most of them in drivers/net/.
      Should I split my patch for each subnet directories ? (wireless/, wan/, etc)
      
      Thanks to Thomas Surrel for helping me refining my semantic patch.
      Signed-off-by: NYoann Padioleau <padator@wanadoo.fr>
      
       3c359.c       |   58 +++++++++++++++++++++++++++++-----------------------------
       ibmtr.c       |   38 +++++++++++++++++++-------------------
       lanstreamer.c |   32 ++++++++++++++++----------------
       madgemc.c     |    4 ++--
       olympic.c     |   36 ++++++++++++++++++------------------
       tmspci.c      |    4 ++--
       6 files changed, 86 insertions(+), 86 deletions(-)
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      eda10531
  2. 04 10月, 2006 1 次提交
  3. 03 7月, 2006 1 次提交
  4. 20 8月, 2005 1 次提交
  5. 31 7月, 2005 1 次提交
    • J
      [PATCH] tms380tr: move to DMA API · 504ff16c
      Jochen Friedrich 提交于
      This patch makes tms380tr use the new DMA API.  Now that on Alpha, this API
      also supports bus master DMA for ISA (platform) devices, i changed the
      driver to use this new API.
      
      This also works around a bug in the firmware loader: The example provided
      in Documentation/firmware_class no longer works, as the firmware loader now
      calls get_kobj_path_length() and the kernel promptly oopses, as the
      home-grown device doesn't have a parent.  Of course, this doesn't happen
      with a "real" device which has its bus (or pseudo bus in the case of
      platform) as parent.
      
      Converted tms380tr to use new DMA API:
        - proteon.c, skisa.c: use platform pseudo bus to create a struct device
        - Space.c: delete init hooks
        - abyss.c, tmspci.c: pass struct device to tms380tr.c
        - tms380tr.c, tms380tr.h: new DMA API, use real device fo firmware loader
      Signed-off-by: NJochen Friedrich <jochen@scram.de>
      Cc: Jeff Garzik <jgarzik@pobox.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      504ff16c
  6. 27 6月, 2005 1 次提交
  7. 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