public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Kuniyuki Iwashima <kuniyu@amazon•com>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
	pabeni@redhat•com, dsahern@kernel•org, kuni1840@gmail•com,
	netdev@vger•kernel.org
Subject: Re: [PATCH v2 net-next 0/2] ipv6: Random cleanup for in6addr_any.
Date: Wed, 29 Mar 2023 08:00:25 +0000	[thread overview]
Message-ID: <168007682563.9659.522742483015153716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230327235455.52990-1-kuniyu@amazon.com>

Hello:

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

On Mon, 27 Mar 2023 16:54:53 -0700 you wrote:
> The first patch removes in6addr_any alternatives and the second
> removes redundant initialisation of a local variable.
> 
> 
> Changes:
>   v2: Use ipv6_addr_any() in patch 1. (David Ahern)
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/2] ipv6: Remove in6addr_any alternatives.
    https://git.kernel.org/netdev/net-next/c/8cdc3223e78c
  - [v2,net-next,2/2] 6lowpan: Remove redundant initialisation.
    https://git.kernel.org/netdev/net-next/c/be689c719eb6

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



      parent reply	other threads:[~2023-03-29  8:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 23:54 [PATCH v2 net-next 0/2] ipv6: Random cleanup for in6addr_any Kuniyuki Iwashima
2023-03-27 23:54 ` [PATCH v2 net-next 1/2] ipv6: Remove in6addr_any alternatives Kuniyuki Iwashima
2023-03-28  6:27   ` Mark Bloch
2023-03-28 14:32   ` David Ahern
2023-03-27 23:54 ` [PATCH v2 net-next 2/2] 6lowpan: Remove redundant initialisation Kuniyuki Iwashima
2023-03-28  6:27   ` Mark Bloch
2023-03-28 19:00     ` Kuniyuki Iwashima
2023-03-29  8: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=168007682563.9659.522742483015153716.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=dsahern@kernel$(echo .)org \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=kuni1840@gmail$(echo .)com \
    --cc=kuniyu@amazon$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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