From: Ben Hutchings <bhutchings@solarflare.com>
To: Somnath Kotur <somnath.kotur@emulex.com>
Cc: <netdev@vger.kernel.org>, Suresh Reddy <suresh.reddy@emulex.com>
Subject: Re: [PATCH net-next v5] be2net: Fix to allow get/set of debug levels in the firmware.
Date: Fri, 18 May 2012 16:24:27 +0100 [thread overview]
Message-ID: <1337354667.2696.3.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <66e444e7-aef9-4ce5-a695-10a70fe3b31e@exht1.ad.emulex.com>
On Fri, 2012-05-18 at 14:29 +0530, Somnath Kotur wrote:
> Patch re-spin.
> Incorporated review comments by Ben Hutchings.
>
> Signed-off-by: Suresh Reddy <suresh.reddy@emulex.com>
> Signed-off-by: Somnath Kotur <somnath.kotur@emulex.com>
Acked-by: Ben Hutchings <bhutchings@solarflare.com>
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2012-05-18 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 8:59 [PATCH net-next v5] be2net: Fix to allow get/set of debug levels in the firmware Somnath Kotur
2012-05-18 15:24 ` Ben Hutchings [this message]
2012-05-18 17:33 ` 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=1337354667.2696.3.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=somnath.kotur@emulex.com \
--cc=suresh.reddy@emulex.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).