From: David Miller <davem@davemloft.net>
To: yuvalmin@broadcom.com
Cc: netdev@vger.kernel.org, ariele@broadcom.com, eilong@broadcom.com
Subject: Re: [PATCH net-next 0/5] bnx2x: Enhancements patch series
Date: Wed, 24 Apr 2013 16:35:29 -0400 (EDT) [thread overview]
Message-ID: <20130424.163529.326546938987869912.davem@davemloft.net> (raw)
In-Reply-To: <1366803902-17870-1-git-send-email-yuvalmin@broadcom.com>
From: "Yuval Mintz" <yuvalmin@broadcom.com>
Date: Wed, 24 Apr 2013 14:44:57 +0300
> This patch series contains several enhancements, as well as small fixes:
>
> - Patch [1/5] - Prevent a theoretical problem in our GRO implementation.
>
> - Patch [2/5] - Support Rx/Tx pause control configuration in autoneg.
>
> - Patch [3/5] - Enhance support for VF's MAC setting and removal.
>
> - Patch [4/5] - Fix a small memory leak between bnx2x and cnic.
>
> - Patch [5/5] - Allow bnx2x to recover after a second slot reset.
>
> Please consider applying these patches to `net-next'.
Applied, but please give a more detailed and verbose top-level description
of what is happening in the series in your "0/N" emails.
You're just regurgitating the git shortlog output, anybody can see that
in the repo itself. The idea of the "0/N" message body is to explain the
series from a high level.
prev parent reply other threads:[~2013-04-24 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 11:44 [PATCH net-next 0/5] bnx2x: Enhancements patch series Yuval Mintz
2013-04-24 11:44 ` [PATCH net-next 1/5] bnx2x: prevent GRO false checksum claims Yuval Mintz
2013-04-24 11:44 ` [PATCH net-next 2/5] bnx2x: Allow RX/TX pause control in autoneg Yuval Mintz
2013-04-24 11:45 ` [PATCH net-next 3/5] bnx2x: Enhance MAC configuration for VFs Yuval Mintz
2013-04-24 11:45 ` [PATCH net-next 4/5] bnx2x: Fix memory leak Yuval Mintz
2013-04-24 11:45 ` [PATCH net-next 5/5] bnx2x: Allow recovery from second slot reset Yuval Mintz
2013-04-24 20:35 ` 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=20130424.163529.326546938987869912.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ariele@broadcom.com \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=yuvalmin@broadcom.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).