From: Jeff Garzik <jgarzik@pobox.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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: Fri, 04 Apr 2008 01:46:05 -0400 [thread overview]
Message-ID: <47F5C09D.5000200@pobox.com> (raw)
In-Reply-To: <20080402093956.2520ebfd@extreme>
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
next prev parent reply other threads:[~2008-04-04 5:46 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 [this message]
2008-04-04 5:52 ` Andrew Morton
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=47F5C09D.5000200@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=cesarb@cesarb.net \
--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).