From: David Miller <davem@davemloft.net>
To: dhananjay@netxen.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH NEXT 0/6] netxen: changes for new chip
Date: Wed, 28 Oct 2009 04:11:39 -0700 (PDT) [thread overview]
Message-ID: <20091028.041139.97336548.davem@davemloft.net> (raw)
In-Reply-To: <1256436243-5736-1-git-send-email-dhananjay@netxen.com>
From: Dhananjay Phadke <dhananjay@netxen.com>
Date: Sat, 24 Oct 2009 19:03:57 -0700
> Series of 6 patches for net-next-2.6, please apply.
All applied, thanks.
prev parent reply other threads:[~2009-10-28 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 2:03 [PATCH NEXT 0/6] netxen: changes for new chip Dhananjay Phadke
2009-10-25 2:03 ` [PATCH NEXT 1/6] netxen: support for new firmware file format Dhananjay Phadke
2009-10-25 2:03 ` [PATCH NEXT 2/6] netxen: refactor indirect register access Dhananjay Phadke
2009-10-25 2:04 ` [PATCH NEXT 3/6] netxen: add PCI IDs for new chip Dhananjay Phadke
2009-10-25 2:04 ` [PATCH NEXT 4/6] netxen: update module info Dhananjay Phadke
2009-10-25 2:04 ` [PATCH NEXT 5/6] netxen: module firmware hints Dhananjay Phadke
2009-10-25 2:04 ` [PATCH NEXT 6/6] netxen: update version to 4.0.65 Dhananjay Phadke
2009-10-28 11:11 ` David Miller [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=20091028.041139.97336548.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dhananjay@netxen.com \
--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