All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	dsahern@kernel.org, nicolas.dichtel@6wind.com,
	netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net 0/2] inet: fix NLM_F_DUMP_INTR logic
Date: Sun, 18 Feb 2024 10:30:26 +0000	[thread overview]
Message-ID: <170825222631.22893.4883215355646209691.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240215172107.3461054-1-edumazet@google.com>

Hello:

This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Thu, 15 Feb 2024 17:21:05 +0000 you wrote:
> Make sure NLM_F_DUMP_INTR is generated if dev_base_seq and
> dev_addr_genid are changed by the same amount.
> 
> Eric Dumazet (2):
>   ipv4: properly combine dev_base_seq and ipv4.dev_addr_genid
>   ipv6: properly combine dev_base_seq and ipv6.dev_addr_genid
> 
> [...]

Here is the summary with links:
  - [net,1/2] ipv4: properly combine dev_base_seq and ipv4.dev_addr_genid
    https://git.kernel.org/netdev/net/c/081a0e3b0d4c
  - [net,2/2] ipv6: properly combine dev_base_seq and ipv6.dev_addr_genid
    https://git.kernel.org/netdev/net/c/e898e4cd1aab

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



      parent reply	other threads:[~2024-02-18 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 17:21 [PATCH net 0/2] inet: fix NLM_F_DUMP_INTR logic Eric Dumazet
2024-02-15 17:21 ` [PATCH net 1/2] ipv4: properly combine dev_base_seq and ipv4.dev_addr_genid Eric Dumazet
2024-02-16  9:16   ` Nicolas Dichtel
2024-02-15 17:21 ` [PATCH net 2/2] ipv6: properly combine dev_base_seq and ipv6.dev_addr_genid Eric Dumazet
2024-02-16  9:17   ` Nicolas Dichtel
2024-02-16  9:19     ` Eric Dumazet
2024-02-18 10:30 ` 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=170825222631.22893.4883215355646209691.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --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.