netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sriharsha.basavapatna@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] be2net: patch-set
Date: Sun, 09 Oct 2016 09:31:23 -0400 (EDT)	[thread overview]
Message-ID: <20161009.093123.2169328494259664121.davem@davemloft.net> (raw)
In-Reply-To: <20161009042853.20601-1-sriharsha.basavapatna@broadcom.com>

From: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Date: Sun,  9 Oct 2016 09:58:48 +0530

> The following patch set contains a few bug fixes.
> Please consider applying this to the net-next tree.
> Thanks.
> 
> Patch-1 Obtains proper PF number for BEx chips
> Patch-2 Fixes a FW update issue seen with BEx chips
> Patch-3 Updates copyright string
> Patch-4 Fixes TX stats for TSO packets
> Patch-5 Enables VF link state setting for BE3

Please do not target real bug fixes at net-next, they should
target 'net' instead.

And that's where I have applied this series.

Thanks.

  parent reply	other threads:[~2016-10-09 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-09  4:28 [PATCH net-next 0/5] be2net: patch-set Sriharsha Basavapatna
2016-10-09  4:28 ` [PATCH net-next 1/5] be2net: Provide an alternate way to read pf_num for BEx chips Sriharsha Basavapatna
2016-10-09  4:28 ` [PATCH net-next 2/5] be2net: NCSI FW section should be properly updated with ethtool for BE3 Sriharsha Basavapatna
2016-10-09  4:28 ` [PATCH net-next 3/5] be2net: Update Copyright string in be_hw.h Sriharsha Basavapatna
2016-10-09  4:28 ` [PATCH net-next 4/5] be2net: Fix TX stats for TSO packets Sriharsha Basavapatna
2016-10-09  4:28 ` [PATCH net-next 5/5] be2net: Enable VF link state setting for BE3 Sriharsha Basavapatna
2016-10-09 13:31 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-22  9:28 [PATCH net-next 0/5] be2net patch-set Sathya Perla
2013-04-22 19:50 ` 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=20161009.093123.2169328494259664121.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sriharsha.basavapatna@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).