From: "Jaswinder Singh Rajput" <jaswinderlinux@gmail.com>
To: "Oliver Hartkopp" <oliver@hartkopp.net>,
"David Woodhouse" <dwmw2@infradead.org>
Cc: "Jaswinder Singh Rajput" <jaswinder@infradead.org>,
davem@redhat.com, jgarzik@redhat.com,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, mchan@broadcom.com,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH -net-next 3/4] firmware: convert tg3 driver to request_firmware()
Date: Mon, 5 Jan 2009 19:42:37 +0530 [thread overview]
Message-ID: <3f9a31f40901050612v700d2542r1e3e400bf0fe3d33@mail.gmail.com> (raw)
In-Reply-To: <49620AFE.6040409@hartkopp.net>
On Mon, Jan 5, 2009 at 6:58 PM, Oliver Hartkopp <oliver@hartkopp.net> wrote:
> 077f849de42e58172e25ccb24df4c1a13e82420c ("firmware: convert tg3 driver to
> request_firmware()")
>
> and i discovered that
>
> 1. I needed to compile the tg3 driver as *module* now as it was not able to
> read the firmware when built-in.
>
Please compile it as build in.
David Woodhouse: Do you have any plans to support firmware by using modules.
Thanks,
JSR.
next prev parent reply other threads:[~2009-01-05 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 8:41 [PATCH -net-next 3/4] firmware: convert tg3 driver to request_firmware() Jaswinder Singh Rajput
2009-01-05 0:11 ` David Miller
2009-01-05 13:28 ` Oliver Hartkopp
2009-01-05 13:58 ` Oliver Hartkopp
2009-01-05 14:12 ` Jaswinder Singh Rajput [this message]
2009-01-05 14:22 ` David Woodhouse
2009-01-05 14:47 ` Jaswinder Singh Rajput
2009-01-05 14:58 ` Oliver Hartkopp
2009-01-05 15:06 ` Jaswinder Singh Rajput
2009-01-06 0:01 ` David Miller
2009-01-07 3:17 ` Michael Marineau
2009-01-07 9:31 ` Oliver Hartkopp
2009-01-07 23:06 ` Michael Marineau
2009-01-13 0:10 ` David Miller
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=3f9a31f40901050612v700d2542r1e3e400bf0fe3d33@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jaswinder@infradead.org \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=oliver@hartkopp.net \
/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).