netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ajitk@serverengines.com, ajitkhaparde@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/7] be2net: bug fix for flashing the BladeEngine3 ASIC
Date: Fri, 12 Feb 2010 12:29:15 -0800 (PST)	[thread overview]
Message-ID: <20100212.122915.156042995.davem@davemloft.net> (raw)
In-Reply-To: <20100209113024.GA10453@serverengines.com>

From: Ajit Khaparde <ajitkhaparde@gmail.com>
Date: Tue, 9 Feb 2010 17:00:35 +0530

> Now flashing both BE2 and BE3 devices is supported.
> 
> From: Naresh G <nareshg@serverengines.com>
> Signed-off-by: Ajit Khaparde <ajitk@serverengines.com>

Applied to net-next-2.6

      reply	other threads:[~2010-02-12 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 11:30 [PATCH 2/7] be2net: bug fix for flashing the BladeEngine3 ASIC Ajit Khaparde
2010-02-12 20:29 ` 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=20100212.122915.156042995.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ajitk@serverengines.com \
    --cc=ajitkhaparde@gmail.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;
as well as URLs for NNTP newsgroup(s).