From: Kurt Kanzenbach <kurt@linutronix.de>
To: Jakub Kicinski <kuba@kernel.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, vinschen@redhat.com,
maciej.fijalkowski@intel.com, magnus.karlsson@intel.com,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, bpf@vger.kernel.org
Subject: Re: [PATCH net-next 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2022-02-07
Date: Wed, 09 Feb 2022 09:13:36 +0100 [thread overview]
Message-ID: <87sfssv4nj.fsf@kurt> (raw)
In-Reply-To: <20220208211305.47dc605f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
Hi Tony,
On Tue Feb 08 2022, Jakub Kicinski wrote:
> On Mon, 7 Feb 2022 15:32:44 -0800 Tony Nguyen wrote:
>> Corinna Vinschen says:
>>
>> 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.
>
> Why -next?
Can we get these patches into net, please? The mentioned igc problem
exists on v5.15-LTS too.
FWIW, Tested-by: Kurt Kanzenbach <kurt@linutronix.de>
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-02-09 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 23:32 [PATCH net-next 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2022-02-07 Tony Nguyen
2022-02-07 23:32 ` [PATCH net-next 1/2] igc: avoid kernel warning when changing RX ring parameters Tony Nguyen
2022-02-07 23:32 ` [PATCH net-next 2/2] igb: refactor XDP registration Tony Nguyen
2022-02-09 5:13 ` [PATCH net-next 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2022-02-07 Jakub Kicinski
2022-02-09 8:13 ` Kurt Kanzenbach [this message]
2022-02-09 17:20 ` Nguyen, Anthony L
2022-02-09 18:22 ` Kurt Kanzenbach
2022-02-09 12:00 ` patchwork-bot+netdevbpf
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=87sfssv4nj.fsf@kurt \
--to=kurt@linutronix.de \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vinschen@redhat.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).