netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Li <lipeng321@huawei.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linuxarm@huawei.com>, <salil.mehta@huawei.com>,
	<lipeng321@huawei.com>
Subject: [PATCH net-next 0/9] fixes for configuration lost problems
Date: Fri, 9 Mar 2018 10:36:55 +0800	[thread overview]
Message-ID: <1520563024-94811-1-git-send-email-lipeng321@huawei.com> (raw)

This patchset refactors some functions and some bugs in order
to fix the configuration loss problem when resetting and
setting channel number.

Yunsheng Lin (9):
  net: hns3: refactor the hclge_get/set_rss function
  net: hns3: refactor the hclge_get/set_rss_tuple function
  net: hns3: fix for RSS configuration loss problem during reset
  net: hns3: fix for pause configuration lost during reset
  net: hns3: fix for use-after-free when setting ring parameter
  net: hns3: refactor the get/put_vector function
  net: hns3: fix for coalesce configuration lost during reset
  net: hns3: refactor the coalesce related struct
  net: hns3: fix for coal configuation lost when setting the channel

 drivers/net/ethernet/hisilicon/hns3/hnae3.h        |   3 +
 drivers/net/ethernet/hisilicon/hns3/hns3_enet.c    | 249 +++++++++++++++------
 drivers/net/ethernet/hisilicon/hns3/hns3_enet.h    |  10 +-
 drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.c |  26 ++-
 .../net/ethernet/hisilicon/hns3/hns3pf/hclge_dcb.c |   2 +
 .../ethernet/hisilicon/hns3/hns3pf/hclge_main.c    | 235 +++++++++----------
 .../ethernet/hisilicon/hns3/hns3pf/hclge_main.h    |  16 ++
 .../ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c  |  12 +-
 8 files changed, 351 insertions(+), 202 deletions(-)

-- 
2.9.3

             reply	other threads:[~2018-03-09  2:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  2:36 Peng Li [this message]
2018-03-09  2:36 ` [PATCH net-next 1/9] net: hns3: refactor the hclge_get/set_rss function Peng Li
2018-03-09  2:36 ` [PATCH net-next 2/9] net: hns3: refactor the hclge_get/set_rss_tuple function Peng Li
2018-03-09  2:36 ` [PATCH net-next 3/9] net: hns3: fix for RSS configuration loss problem during reset Peng Li
2018-03-09  2:36 ` [PATCH net-next 4/9] net: hns3: fix for pause configuration lost " Peng Li
2018-03-09  2:37 ` [PATCH net-next 5/9] net: hns3: fix for use-after-free when setting ring parameter Peng Li
2018-03-09  2:37 ` [PATCH net-next 6/9] net: hns3: refactor the get/put_vector function Peng Li
2018-03-09  2:37 ` [PATCH net-next 7/9] net: hns3: fix for coalesce configuration lost during reset Peng Li
2018-03-09  2:37 ` [PATCH net-next 8/9] net: hns3: refactor the coalesce related struct Peng Li
2018-03-09  2:37 ` [PATCH net-next 9/9] net: hns3: fix for coal configuation lost when setting the channel Peng Li
2018-03-09 16:34 ` [PATCH net-next 0/9] fixes for configuration lost problems 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=1520563024-94811-1-git-send-email-lipeng321@huawei.com \
    --to=lipeng321@huawei.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=salil.mehta@huawei.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).