From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: <intel-wired-lan@lists.osuosl.org>
Cc: Magnus Karlsson <magnus.karlsson@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v2] ixgbe: XDP: fix checker warning from rcu pointer
Date: Tue, 22 Nov 2022 15:54:42 -0800 [thread overview]
Message-ID: <fd80722c-d4d7-1ce4-82da-2e71566ff0ba@intel.com> (raw)
In-Reply-To: <20221122234825.3360663-1-jesse.brandeburg@intel.com>
On 11/22/2022 3:48 PM, Jesse Brandeburg wrote:
> The ixgbe driver uses an older style failure mode when initializing the
> XDP program and the queues. It causes some warnings when running C=2
> checking builds (and it's the last one in the ethernet/intel tree).
Um yeah, I forgot to remove the v2 from the title. This is only v1...
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-11-22 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 23:48 [Intel-wired-lan] [PATCH net-next v2] ixgbe: XDP: fix checker warning from rcu pointer Jesse Brandeburg
2022-11-22 23:54 ` Jesse Brandeburg [this message]
2022-11-23 15:39 ` Maciej Fijalkowski
2022-12-12 4:29 ` Rout, ChandanX
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=fd80722c-d4d7-1ce4-82da-2e71566ff0ba@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=magnus.karlsson@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