netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: rmody@brocade.com
Cc: netdev@vger.kernel.org, adapter_linux_open_src_team@brocade.com
Subject: Re: [net-next 0/7] bna: H/W enablement and update driver version to 3.0.2.2
Date: Wed, 28 Sep 2011 02:59:37 -0400 (EDT)	[thread overview]
Message-ID: <20110928.025937.1162448846487782731.davem@davemloft.net> (raw)
In-Reply-To: <1317155951-17242-1-git-send-email-rmody@brocade.com>

From: Rasesh Mody <rmody@brocade.com>
Date: Tue, 27 Sep 2011 13:39:04 -0700

> Hi Dave,
> 
>    The following series is re-submitted. These patches add support for
>    Brocade-1860 Fabric Adapter and address the comments received from
>    upstream community.
> 
>    It updates the Brocade BNA driver to v3.0.2.2.
> 
>    The driver has been compiled & tested against net-next-2.6(3.0.0-rc7).

All applied, thanks.

  parent reply	other threads:[~2011-09-28  7:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 20:39 [net-next 0/7] bna: H/W enablement and update driver version to 3.0.2.2 Rasesh Mody
2011-09-27 20:39 ` [net-next 1/7] bna: Brocade 1860 IOC PLL, Reg Defs and ASIC Mode Changes Rasesh Mody
2011-09-27 23:26   ` Joe Perches
2011-09-27 20:39 ` [net-next 2/7] bna: Capability Map and MFG Block Changes for New HW Rasesh Mody
2011-09-27 20:39 ` [net-next 3/7] bna: Implement FW Download " Rasesh Mody
2011-09-27 20:39 ` [net-next 4/7] bna: Brocade 1860 HW Enablement Rasesh Mody
2011-09-27 20:39 ` [net-next 5/7] bna: PLL Init Fix and Add Stats Attributes Rasesh Mody
2011-09-27 20:39 ` [net-next 6/7] bna: Add Callback to Fix RXQ Stop Rasesh Mody
2011-09-27 20:39 ` [net-next 7/7] bna: Driver Version changed to 3.0.2.2 Rasesh Mody
2011-09-28  6:59 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-09-26 21:12 [net-next 0/7] bna: H/W enablement and update driver version " Rasesh Mody
2011-09-24  2:14 Rasesh Mody

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=20110928.025937.1162448846487782731.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).