From: David Miller <davem@davemloft.net>
To: dhananjay@netxen.com
Cc: davem@davemloft.com, netdev@vger.kernel.org
Subject: Re: [PATCH NEXT 3/4] netxen: remove netxen_nic_niu.c
Date: Wed, 26 Aug 2009 15:37:53 -0700 (PDT) [thread overview]
Message-ID: <20090826.153753.223038717.davem@davemloft.net> (raw)
In-Reply-To: <1251177808-16450-3-git-send-email-dhananjay@netxen.com>
From: Dhananjay Phadke <dhananjay@netxen.com>
Date: Mon, 24 Aug 2009 22:23:27 -0700
> Consolidate all MAC/PHY access functions into netxen_nic_hw.c
>
> Signed-off-by: Dhananjay Phadke <dhananjay@netxen.com>
Applied.
next prev parent reply other threads:[~2009-08-26 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 5:23 [PATCH NEXT 1/4] netxen: remove unused code Dhananjay Phadke
2009-08-25 5:23 ` [PATCH NEXT 2/4] netxen: implement generic pcie semaphore functions Dhananjay Phadke
2009-08-26 22:37 ` David Miller
2009-08-25 5:23 ` [PATCH NEXT 3/4] netxen: remove netxen_nic_niu.c Dhananjay Phadke
2009-08-26 22:37 ` David Miller [this message]
2009-08-25 5:23 ` [PATCH NEXT 4/4] netxen: bridged mode optimizations Dhananjay Phadke
2009-08-26 22:37 ` David Miller
2009-08-26 22:37 ` [PATCH NEXT 1/4] netxen: remove unused code 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=20090826.153753.223038717.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davem@davemloft.com \
--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