All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: netdev <netdev@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: Network: convert network devices to use struct device instead of class_device
Date: Thu, 08 Feb 2007 07:43:18 -0500	[thread overview]
Message-ID: <45CB1AE6.9020707@garzik.org> (raw)
In-Reply-To: <200702080400.l1840lFd002314@hera.kernel.org>

Linux Kernel Mailing List wrote:
> Gitweb:     http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=43cb76d91ee85f579a69d42bc8efc08bac560278
> Commit:     43cb76d91ee85f579a69d42bc8efc08bac560278
> Parent:     2943ecf2ed32632473c06f1975db47a7aa98c10f
> Author:     Greg Kroah-Hartman <gregkh@suse.de>
> AuthorDate: Tue Apr 9 12:14:34 2002 -0700
> Committer:  Greg Kroah-Hartman <gregkh@suse.de>
> CommitDate: Wed Feb 7 10:37:11 2007 -0800
> 
>     Network: convert network devices to use struct device instead of class_device
>     
>     This lets the network core have the ability to handle suspend/resume
>     issues, if it wants to.
>     
>     Thanks to Frederik Deweerdt <frederik.deweerdt@gmail.com> for the arm
>     driver fixes.
>     
>     Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> ---
>  drivers/infiniband/ulp/ipoib/ipoib_main.c |   33 ++--
>  drivers/infiniband/ulp/ipoib/ipoib_vlan.c |   11 +-
>  drivers/net/arm/at91_ether.c              |    2 +-
>  drivers/net/arm/etherh.c                  |    2 +-
>  drivers/net/bonding/bond_sysfs.c          |  287 +++++++++++++++++-----------
>  drivers/net/iseries_veth.c                |    2 +-
>  drivers/net/macb.c                        |   36 ++--
>  drivers/net/smc911x.c                     |    2 +-
>  drivers/net/smc91x.c                      |    2 +-
>  drivers/net/wireless/hostap/hostap_main.c |    2 +-
>  drivers/net/wireless/orinoco.c            |    4 +-
>  drivers/net/wireless/orinoco_cs.c         |    2 +-
>  drivers/net/wireless/spectrum_cs.c        |    2 +-
>  include/linux/netdevice.h                 |    5 +-
>  net/bridge/br_if.c                        |    2 +-
>  net/bridge/br_sysfs_br.c                  |  234 +++++++++++++-----------
>  net/bridge/br_sysfs_if.c                  |    2 +-
>  net/core/dev.c                            |    6 +-
>  net/core/net-sysfs.c                      |  175 ++++++++++--------
>  net/core/skbuff.c                         |    2 +-
>  20 files changed, 451 insertions(+), 362 deletions(-)

It's highly disappointing that this was never discussed on 
netdev@vger.kernel.org, or even CC'd to me.

	Jeff



       reply	other threads:[~2007-02-08 12:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200702080400.l1840lFd002314@hera.kernel.org>
2007-02-08 12:43 ` Jeff Garzik [this message]
2007-02-08 15:41   ` Network: convert network devices to use struct device instead of class_device Stephen Hemminger
2007-02-08 17:29     ` Dmitry Torokhov
2007-02-09  0:56       ` Greg KH
2007-02-09  3:59         ` Dmitry Torokhov
2007-02-09  8:22           ` Kay Sievers
2007-02-09 15:28             ` Dmitry Torokhov
2007-02-09 16:48           ` Greg KH
2007-02-20 15:15         ` Dmitry Torokhov
2007-02-09  0:52     ` Greg KH
2007-02-09  0:51   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45CB1AE6.9020707@garzik.org \
    --to=jeff@garzik.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.