From: David Miller <davem@davemloft.net>
To: rmody@brocade.com
Cc: netdev@vger.kernel.org, adapter_linux_open_src_team@brocade.com
Subject: Re: [PATCH 0/8] bna: Update bna driver version to 3.0.2.0
Date: Thu, 11 Aug 2011 07:33:01 -0700 (PDT) [thread overview]
Message-ID: <20110811.073301.1338953611842014342.davem@davemloft.net> (raw)
In-Reply-To: <1312856502-31242-1-git-send-email-rmody@brocade.com>
From: Rasesh Mody <rmody@brocade.com>
Date: Mon, 8 Aug 2011 19:21:34 -0700
> The following patch set contains changes for driver re-architecture and
> code re-organisazion. This includes driver firmware interface change,
> tx and rx re-design and corresponding changes required to use/enable new
> code and also keep the patch set bisectable. It also removes obsolete
> files and cleans up unused code.
>
> This updates the Brocade BNA driver to v3.0.2.0.
>
> The driver has been compiled & tested against net-next-2.6(3.0.0-rc7)
All applied, thanks.
prev parent reply other threads:[~2011-08-11 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 2:21 [PATCH 0/8] bna: Update bna driver version to 3.0.2.0 Rasesh Mody
2011-08-09 2:21 ` [PATCH 1/8] bna: MSGQ Implementation Rasesh Mody
2011-08-09 2:21 ` [PATCH 2/8] bna: Introduce ENET as New Driver and FW Interface Rasesh Mody
2011-08-09 2:21 ` [PATCH 3/8] bna: Tx and Rx Redesign Rasesh Mody
2011-08-09 2:21 ` [PATCH 4/8] bna: Add New HW Defs Rasesh Mody
2011-08-09 2:21 ` [PATCH 5/8] bna: ENET and Tx Rx Redesign Enablement Rasesh Mody
2011-08-09 2:21 ` [PATCH 6/8] bna: Remove Unused Code Rasesh Mody
2011-08-09 2:21 ` [PATCH 7/8] bna: Remove Obsolete Files Rasesh Mody
2011-08-09 2:21 ` [PATCH 8/8] bna: Driver Version changed to 3.0.2.0 Rasesh Mody
2011-08-11 14:33 ` 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=20110811.073301.1338953611842014342.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adapter_linux_open_src_team@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=rmody@brocade.com \
/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).