netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
	netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
	Cesar Eduardo Barros <cesarb@cesarb.net>,
	tom@sharkbay.at
Subject: Re: [PATCH] sc92031: sysfs link missing
Date: Thu, 3 Apr 2008 22:52:16 -0700	[thread overview]
Message-ID: <20080403225216.4d2388cc.akpm@linux-foundation.org> (raw)
In-Reply-To: <47F5C09D.5000200@pobox.com>

On Fri, 04 Apr 2008 01:46:05 -0400 Jeff Garzik <jgarzik@pobox.com> wrote:

> Stephen Hemminger wrote:
> > Add missing sysfs device association. Compile tested only -ENOHW.
> > 
> > Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
> > 
> > 
> > --- a/drivers/net/sc92031.c	2008-04-02 09:34:35.000000000 -0700
> > +++ b/drivers/net/sc92031.c	2008-04-02 09:36:53.000000000 -0700
> > @@ -1446,6 +1446,7 @@ static int __devinit sc92031_probe(struc
> >  	}
> >  
> >  	pci_set_drvdata(pdev, dev);
> > +	SET_NETDEV_DEV(dev, &hw->pdev->dev);
> >  
> >  #if SC92031_USE_BAR == 0
> >  	dev->mem_start = pci_resource_start(pdev, SC92031_USE_BAR);
> 
> applied
> 

That's version 1.  There was a super-optimised version 2:



From: Stephen Hemminger <shemminger@vyatta.com>

Add missing sysfs device association. Compile tested only -ENOHW.

Addresses http://bugzilla.kernel.org/show_bug.cgi?id=10380

Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Cc: Jeff Garzik <jgarzik@pobox.com>
Cc: Cesar Eduardo Barros <cesarb@cesarb.net>
Cc: <tom@sharkbay.at>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 drivers/net/sc92031.c |    1 +
 1 file changed, 1 insertion(+)

diff -puN drivers/net/sc92031.c~sc92031-sysfs-link-missing drivers/net/sc92031.c
--- a/drivers/net/sc92031.c~sc92031-sysfs-link-missing
+++ a/drivers/net/sc92031.c
@@ -1446,6 +1446,7 @@ static int __devinit sc92031_probe(struc
 	}
 
 	pci_set_drvdata(pdev, dev);
+	SET_NETDEV_DEV(dev, &pdev->dev);
 
 #if SC92031_USE_BAR == 0
 	dev->mem_start = pci_resource_start(pdev, SC92031_USE_BAR);
_


  reply	other threads:[~2008-04-04  5:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10380-10286@http.bugzilla.kernel.org/>
2008-04-02 16:14 ` [Bugme-new] [Bug 10380] New: sc92031 does not create a device link in sysfs Andrew Morton
2008-04-02 16:39   ` [PATCH] sc92031: sysfs link missing Stephen Hemminger
2008-04-04  5:46     ` Jeff Garzik
2008-04-04  5:52       ` Andrew Morton [this message]
2008-04-04  6:40         ` Jeff Garzik
2008-04-02 16:49   ` [Bugme-new] [Bug 10380] New: sc92031 does not create a device link in sysfs Stephen Hemminger
2008-04-02 17:08     ` [PATCH 1/3] sc92031: use net_device stats Stephen Hemminger
2008-04-02 17:08     ` [Bugme-new] [Bug 10380] New: sc92031 does not create a device link in sysfs Thomas Scheiblauer
2008-04-02 17:11     ` [PATCH 2/3] sc92031: start transmit return value bugfix Stephen Hemminger
2008-04-02 17:11     ` [PATCH 1/3] sc92031: use net_device stats Stephen Hemminger
2008-04-12  9:02       ` Jeff Garzik
2008-04-02 17:13     ` [PATCH 3/3] sc92031: use netdev_alloc_skb Stephen Hemminger

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=20080403225216.4d2388cc.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=cesarb@cesarb.net \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=tom@sharkbay.at \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).