From: Ben Hutchings <bhutchings@solarflare.com>
To: Jaswinder Singh <jaswinderlinux@gmail.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
Subject: Re: Firmware patches for Network
Date: Fri, 19 Dec 2008 19:46:11 +0000 [thread overview]
Message-ID: <1229715971.3097.6.camel@achroite> (raw)
In-Reply-To: <3f9a31f40812191131m48802157r596d7773fb435f34@mail.gmail.com>
On Sat, 2008-12-20 at 01:01 +0530, Jaswinder Singh wrote:
[...]
> Please let me know, should I update these patches for :
[...]
> 3. git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
This one.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2008-12-19 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 19:31 Firmware patches for Network Jaswinder Singh
2008-12-19 19:46 ` Ben Hutchings [this message]
2008-12-19 20:11 ` Jaswinder Singh
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=1229715971.3097.6.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=jaswinderlinux@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).