All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dmitry Skorodumov <dskr99@gmail.com>
Cc: netdev@vger.kernel.org, skorodumov.dmitry@huawei.com
Subject: Re: [PATCH v5 net 0/2] ipvlan: addrs_lock made per port
Date: Mon, 19 Jan 2026 18:10:10 +0000	[thread overview]
Message-ID: <176884621003.85277.11896348581654872736.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260112142417.4039566-1-skorodumov.dmitry@huawei.com>

Hello:

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

On Mon, 12 Jan 2026 17:24:05 +0300 you wrote:
> First patch fixes a rather minor issues that sometimes
> ipvlan-addrs are modified without lock (because
> for IPv6 addr can be sometimes added without RTNL)
> 
> diff from v4:
>   - Patch 2 (selftests): execution time of sub-script is limited with 1 minute.
> 
> [...]

Here is the summary with links:
  - [v5,net,1/2] ipvlan: Make the addrs_lock be per port
    https://git.kernel.org/netdev/net/c/d3ba32162488
  - [v5,net,2/2] selftests: net: simple selftest for ipvtap
    https://git.kernel.org/netdev/net/c/8becfe16e4a1

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



      parent reply	other threads:[~2026-01-19 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 14:24 [PATCH v5 net 0/2] ipvlan: addrs_lock made per port Dmitry Skorodumov
2026-01-12 14:24 ` [PATCH v5 net 1/2] ipvlan: Make the addrs_lock be " Dmitry Skorodumov
2026-01-12 14:24 ` [PATCH v5 net 2/2] selftests: net: simple selftest for ipvtap Dmitry Skorodumov
2026-01-19 18:10 ` 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=176884621003.85277.11896348581654872736.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dskr99@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=skorodumov.dmitry@huawei.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.