From: Kurt Kanzenbach <kurt@linutronix•de>
To: "Nguyen, Anthony L" <anthony.l.nguyen@intel•com>,
"Gomes, Vinicius" <vinicius.gomes@intel•com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel•com>
Cc: "davem@davemloft•net" <davem@davemloft•net>,
"andre.guedes@intel•com" <andre.guedes@intel•com>,
"Joseph, Jithu" <jithu.joseph@intel•com>,
"john.fastabend@gmail•com" <john.fastabend@gmail•com>,
"daniel@iogearbox•net" <daniel@iogearbox•net>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel•com>,
"hawk@kernel•org" <hawk@kernel•org>,
"ast@kernel•org" <ast@kernel•org>,
"kuba@kernel•org" <kuba@kernel•org>,
"vedang.patel@intel•com" <vedang.patel@intel•com>,
"intel-wired-lan@lists•osuosl.org"
<intel-wired-lan@lists•osuosl.org>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: [PATCH net] igc: Clear old XDP info when changing ring settings
Date: Sat, 05 Feb 2022 10:57:52 +0100 [thread overview]
Message-ID: <87iltttz33.fsf@kurt> (raw)
In-Reply-To: <0f1e1c0fc4f555ef0eaaa983da6d8f012a0acf60.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
On Fri Feb 04 2022, Anthony L. Nguyen wrote:
> Thanks for the patch, but we have a patch[1] to resolve this issue in a
> more preferred method. igb is actually changing as well to this new
> solution [2].
OK, great.
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
prev parent reply other threads:[~2022-02-05 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 8:02 [PATCH net] igc: Clear old XDP info when changing ring settings Kurt Kanzenbach
2022-02-04 17:04 ` Nguyen, Anthony L
2022-02-05 9:57 ` Kurt Kanzenbach [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=87iltttz33.fsf@kurt \
--to=kurt@linutronix$(echo .)de \
--cc=andre.guedes@intel$(echo .)com \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=hawk@kernel$(echo .)org \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=jithu.joseph@intel$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=maciej.fijalkowski@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=vedang.patel@intel$(echo .)com \
--cc=vinicius.gomes@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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