netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: intel-wired-lan@osuosl.org, netdev@vger.kernel.org,
	Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cc: Lennert Buytenhek <buytenh@wantstofly.org>,
	Alexander Lobakin <alexandr.lobakin@intel.com>
Subject: [PATCH 0/2 net-next v6] igb/igc: fix XDP registration
Date: Wed, 19 Jan 2022 15:52:57 +0100	[thread overview]
Message-ID: <20220119145259.1790015-1-vinschen@redhat.com> (raw)

Fix the kernel warning "Missing unregister, handled but fix driver"
when running, e.g.,

  $ ethtool -G eth0 rx 1024

on igc.  Remove memset hack from igb and align igb code to igc. 

v3: use dev_err rather than netdev_err, just as in error case.
v4: fix a return copy/pasted from original igc code into the correct
    `goto err', improve commit message.
v5: add missing dma_free_coherent calls in error case.
v6: refactor code to register with XDP first, as in igc originally.

Corinna Vinschen (2):
  igc: avoid kernel warning when changing RX ring parameters
  igb: refactor XDP registration

 drivers/net/ethernet/intel/igb/igb_ethtool.c |  4 ----
 drivers/net/ethernet/intel/igb/igb_main.c    | 19 +++++++++++++------
 drivers/net/ethernet/intel/igc/igc_main.c    |  3 +++
 3 files changed, 16 insertions(+), 10 deletions(-)

-- 
2.27.0


             reply	other threads:[~2022-01-19 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 14:52 Corinna Vinschen [this message]
2022-01-19 14:52 ` [PATCH 1/2 net-next v6] igc: avoid kernel warning when changing RX ring parameters Corinna Vinschen
2022-01-26 17:13   ` Vinicius Costa Gomes
2022-01-19 14:52 ` [PATCH 2/2 net-next v6] igb: refactor XDP registration Corinna Vinschen
2022-01-26 17:14   ` Vinicius Costa Gomes
2022-02-05 12:14   ` [Intel-wired-lan] " Corinna Vinschen
2022-02-07  8:58   ` Penigalapati, Sandeep

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=20220119145259.1790015-1-vinschen@redhat.com \
    --to=vinschen@redhat.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=buytenh@wantstofly.org \
    --cc=intel-wired-lan@osuosl.org \
    --cc=netdev@vger.kernel.org \
    --cc=vinicius.gomes@intel.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).