All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, bartoszx.staszewski@intel.com,
	netdev@vger.kernel.org, maciej.fijalkowski@intel.com,
	magnus.karlsson@intel.com, bjorn@kernel.org, ast@kernel.org,
	daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
	bpf@vger.kernel.org, saeed@kernel.org,
	mateusz.palczewski@intel.com, Shwetha.nagaraju@intel.com
Subject: Re: [PATCH net v3 1/1] i40e: Fix the inability to attach XDP program on downed interface
Date: Mon, 12 Dec 2022 23:30:16 +0000	[thread overview]
Message-ID: <167088781664.32014.2462162392412968800.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221209185411.2519898-1-anthony.l.nguyen@intel.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  9 Dec 2022 10:54:11 -0800 you wrote:
> From: Bartosz Staszewski <bartoszx.staszewski@intel.com>
> 
> Whenever trying to load XDP prog on downed interface, function i40e_xdp
> was passing vsi->rx_buf_len field to i40e_xdp_setup() which was equal 0.
> i40e_open() calls i40e_vsi_configure_rx() which configures that field,
> but that only happens when interface is up. When it is down, i40e_open()
> is not being called, thus vsi->rx_buf_len is not set.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/1] i40e: Fix the inability to attach XDP program on downed interface
    https://git.kernel.org/netdev/net/c/0c87b545a2ed

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-12-12 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 18:54 [PATCH net v3 1/1] i40e: Fix the inability to attach XDP program on downed interface Tony Nguyen
2022-12-09 19:07 ` Saeed Mahameed
2022-12-12 23:30 ` patchwork-bot+netdevbpf [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=167088781664.32014.2462162392412968800.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Shwetha.nagaraju@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=ast@kernel.org \
    --cc=bartoszx.staszewski@intel.com \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=mateusz.palczewski@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeed@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.