public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jeffrey Ji <jeffreyjilinux@gmail.com>
Cc: edumazet@google.com, davem@davemloft.net, brianvv@google.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	kuba@kernel.org, jeffreyji@google.com
Subject: Re: [PATCH v2 net-next] teaming: deliver link-local packets with the link they arrive on
Date: Fri, 18 Feb 2022 11:50:11 +0000	[thread overview]
Message-ID: <164518501174.13243.5915741906688907086.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220217212312.2827792-1-jeffreyji@google.com>

Hello:

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

On Thu, 17 Feb 2022 21:23:12 +0000 you wrote:
> From: jeffreyji <jeffreyji@google.com>
> 
> skb is ignored if team port is disabled. We want the skb to be delivered
> if it's an link layer packet.
> 
> Issue is already fixed for bonding in
> commit b89f04c61efe ("bonding: deliver link-local packets with skb->dev set to link that packets arrived on")
> 
> [...]

Here is the summary with links:
  - [v2,net-next] teaming: deliver link-local packets with the link they arrive on
    https://git.kernel.org/netdev/net-next/c/aaae162aeb67

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



      reply	other threads:[~2022-02-18 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 21:23 [PATCH v2 net-next] teaming: deliver link-local packets with the link they arrive on Jeffrey Ji
2022-02-18 11:50 ` 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=164518501174.13243.5915741906688907086.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=brianvv@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jeffreyji@google.com \
    --cc=jeffreyjilinux@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox