From: "Jaswinder Singh" <jaswinderlinux@gmail.com>
To: "Ben Hutchings" <bhutchings@solarflare.com>
Cc: netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
davem@davemloft.net, "Jeff Garzik" <jeff@garzik.org>,
"David Woodhouse" <dwmw2@infradead.org>,
sfr@canb.auug.org.au, linux-next@vger.kernel.org
Subject: Re: Firmware patches for Network
Date: Sat, 20 Dec 2008 01:41:36 +0530 [thread overview]
Message-ID: <3f9a31f40812191211x12fc08cateb3502c6765d0c4c@mail.gmail.com> (raw)
In-Reply-To: <1229715971.3097.6.camel@achroite>
Hello Ben,
On Sat, Dec 20, 2008 at 1:16 AM, Ben Hutchings
<bhutchings@solarflare.com> wrote:
>> 3. git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
>
> This one.
>
4 out of 10 Networking's firmware patches are already floating in
linux-next from long time :
1. firmware: convert e100 driver to request_firmware()
http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=c98e632b660ef49b67a9591040230b518785e38a
2. firmware: convert acenic driver to request_firmware()
http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=e39c0e190f52331b35931fbe5e34a07114d66171
3. firmware: convert tg3 driver to request_firmware()
http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=aadd3ed38a6745e21dc8d2f388bbba42ead0a085
4. starfire: use request_firmware()
http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=df3eea674103ce451357be8eb873092943ad3551
Should I need to resend all 10 or remaining 6.
Thank you,
Jaswinder Singh.
prev parent reply other threads:[~2008-12-19 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 19:31 Jaswinder Singh
2008-12-19 19:46 ` Ben Hutchings
2008-12-19 20:11 ` Jaswinder Singh [this message]
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=3f9a31f40812191211x12fc08cateb3502c6765d0c4c@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®