From: David Miller <davem@davemloft.net>
To: sathya.perla@emulex.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] be2net: fixes
Date: Mon, 24 Oct 2011 18:35:46 -0400 (EDT) [thread overview]
Message-ID: <20111024.183546.495965585975609045.davem@davemloft.net> (raw)
In-Reply-To: <1319460303-25560-1-git-send-email-sathya.perla@emulex.com>
From: Sathya Perla <sathya.perla@emulex.com>
Date: Mon, 24 Oct 2011 18:14:59 +0530
> Pls apply.
>
> Sathya Perla (4):
> be2net: add vlan/rx-mode/flow-control config to be_setup()
> be2net: refactor VF setup/teardown code into be_vf_setup/clear()
> be2net: don't create multiple TXQs in BE2
> be2net: don't create multiple RX/TX rings in multi channel mode
Applied, but many of your commit messages were poorly formatted (lines
exceeding 80 columns) and patches #1 and #2 had several trailing
whitespace errors.
I fixed this all up, but you have to be better than this.
next prev parent reply other threads:[~2011-10-24 22:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 12:44 [PATCH net-next 0/4] be2net: fixes Sathya Perla
2011-10-24 12:45 ` [PATCH net-next 1/4] be2net: add vlan/rx-mode/flow-control config to be_setup() Sathya Perla
2011-10-24 12:45 ` [PATCH net-next 2/4] be2net: refactor VF setup/teardown code into be_vf_setup/clear() Sathya Perla
2011-10-24 12:45 ` [PATCH net-next 3/4] be2net: don't create multiple TXQs in BE2 Sathya Perla
2011-10-24 12:45 ` [PATCH net-next 4/4] be2net: don't create multiple RX/TX rings in multi channel mode Sathya Perla
2011-10-24 22:35 ` David Miller [this message]
2011-10-25 4:49 ` [PATCH net-next 0/4] be2net: fixes Sathya.Perla
-- strict thread matches above, loose matches on Subject: below --
2011-11-11 5:17 [PATCH net-next 0/4] be2net fixes Sathya Perla
2011-11-12 22:59 ` David Miller
2012-05-02 13:39 Somnath Kotur
2012-05-03 1:07 ` David Miller
[not found] <1335965986-31886-1-git-send-email-somnath.kotur@emulex.com>
2012-05-02 14:04 ` Somnath.Kotur
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=20111024.183546.495965585975609045.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@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).