All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
	pabeni@redhat.com
Subject: Re: [PATCH net 0/2] l3mdev: Fix ip tunnel case after recent l3mdev change
Date: Fri, 15 Apr 2022 21:50:13 +0000	[thread overview]
Message-ID: <165005941314.21261.596606933899156187.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220413174320.28989-1-dsahern@kernel.org>

Hello:

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

On Wed, 13 Apr 2022 11:43:18 -0600 you wrote:
> Second patch provides a fix for ip tunnels after the recent l3mdev change
> that avoids touching the oif in the flow struct. First patch preemptively
> provides a fix to an existing function that the second patch uses.
> 
> David Ahern (2):
>   l3mdev: l3mdev_master_upper_ifindex_by_index_rcu should be using
>     netdev_master_upper_dev_get_rcu
>   net: Handle l3mdev in ip_tunnel_init_flow
> 
> [...]

Here is the summary with links:
  - [net,1/2] l3mdev: l3mdev_master_upper_ifindex_by_index_rcu should be using netdev_master_upper_dev_get_rcu
    https://git.kernel.org/netdev/net/c/83daab06252e
  - [net,2/2] net: Handle l3mdev in ip_tunnel_init_flow
    https://git.kernel.org/netdev/net/c/db53cd3d88dc

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-04-15 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 17:43 [PATCH net 0/2] l3mdev: Fix ip tunnel case after recent l3mdev change David Ahern
2022-04-13 17:43 ` [PATCH net 1/2] l3mdev: l3mdev_master_upper_ifindex_by_index_rcu should be using netdev_master_upper_dev_get_rcu David Ahern
2022-04-13 17:43 ` [PATCH net 2/2] net: Handle l3mdev in ip_tunnel_init_flow David Ahern
2022-04-15 21: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=165005941314.21261.596606933899156187.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.