netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org, idosch@nvidia.com,
	vladimir@nikishkin.pw, mlxsw@nvidia.com
Subject: Re: [PATCH net-next] mlxsw: spectrum_nve_vxlan: Fix unsupported flag regression
Date: Fri, 09 Jun 2023 02:00:20 +0000	[thread overview]
Message-ID: <168627602041.23497.16276136341516762015.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5533e63643bf719bbe286fef60f749c9cad35005.1686139716.git.petrm@nvidia.com>

Hello:

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

On Wed, 7 Jun 2023 14:19:26 +0200 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
> 
> The recently added 'VXLAN_F_LOCALBYPASS' flag is set by default on VXLAN
> devices and denotes a behavior that is irrelevant for the hardware data
> path. Add it to the lists of IPv4 and IPv6 supported flags to avoid
> rejecting offload of VXLAN devices which have this flag set.
> 
> [...]

Here is the summary with links:
  - [net-next] mlxsw: spectrum_nve_vxlan: Fix unsupported flag regression
    https://git.kernel.org/netdev/net-next/c/37ff78e977f1

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



      parent reply	other threads:[~2023-06-09  2:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 12:19 [PATCH net-next] mlxsw: spectrum_nve_vxlan: Fix unsupported flag regression Petr Machata
2023-06-08 10:09 ` Simon Horman
2023-06-09  2:00 ` 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=168627602041.23497.16276136341516762015.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=vladimir@nikishkin.pw \
    /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).