From: David Miller <davem@davemloft.net>
To: chas@cmf.nrl.navy.mil
Cc: netdev@vger.kernel.org
Subject: Re: converting fore200e driver to use request_firmware()
Date: Wed, 06 Feb 2008 16:05:42 -0800 (PST) [thread overview]
Message-ID: <20080206.160542.07994571.davem@davemloft.net> (raw)
In-Reply-To: <200802070001.m1701o8E019626@cmf.nrl.navy.mil>
From: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
Date: Wed, 6 Feb 2008 19:01:50 -0500
> however, i ran into a little problem with the sbus interface. what should
> i pass for 'struct device *' for an sbus device?
"&sdev->ofdev.dev" should work
next prev parent reply other threads:[~2008-02-07 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 0:01 converting fore200e driver to use request_firmware() chas williams - CONTRACTOR
2008-02-07 0:05 ` David Miller [this message]
2008-02-07 19:20 ` chas williams - CONTRACTOR
2008-02-07 19:43 ` 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=20080206.160542.07994571.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chas@cmf.nrl.navy.mil \
--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 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).