All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	tchornyi@marvell.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH V2 net-next] net: marvell: prestera: implement br_port_locked flag offloading
Date: Wed, 24 Aug 2022 12:00:15 +0000	[thread overview]
Message-ID: <166134241536.3394.1114076220521153448.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220822180315.3927-1-oleksandr.mazur@plvision.eu>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 22 Aug 2022 21:03:15 +0300 you wrote:
> Both <port> br_port_locked and <lag> interfaces's flag
> offloading is supported. No new ABI is being added,
> rather existing (port_param_set) API call gets extended.
> 
> Signed-off-by: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
> 
> V2:
>   add missing receipents (linux-kernel, netdev)
> 
> [...]

Here is the summary with links:
  - [V2,net-next] net: marvell: prestera: implement br_port_locked flag offloading
    https://git.kernel.org/netdev/net-next/c/73ef239cd843

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



      reply	other threads:[~2022-08-24 12:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 18:03 [PATCH V2 net-next] net: marvell: prestera: implement br_port_locked flag offloading Oleksandr Mazur
2022-08-24 12: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=166134241536.3394.1114076220521153448.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oleksandr.mazur@plvision.eu \
    --cc=pabeni@redhat.com \
    --cc=tchornyi@marvell.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 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.