Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] ipv6: record frag_max_size in atomic fragments in input
 path
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <162163500961.23315.17400956009063652295.git-patchwork-notify@kernel.org>
Date:   Fri, 21 May 2021 22:10:09 +0000
References: <20210521202115.218095EC05F0@us226.sjc.aristanetworks.com>
In-Reply-To: <20210521202115.218095EC05F0@us226.sjc.aristanetworks.com>
To:     Francesco Ruggeri <fruggeri@arista.com>
Cc:     davem@davemloft.net, linux-kernel@vger.kernel.org,
        netdev@vger.kernel.org, edumazet@google.com, willemb@google.com,
        kuba@kernel.org, dsahern@kernel.org, yoshfuji@linux-ipv6.org
Precedence: bulk

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Fri, 21 May 2021 13:21:14 -0700 you wrote:
> Commit dbd1759e6a9c ("ipv6: on reassembly, record frag_max_size")
> filled the frag_max_size field in IP6CB in the input path.
> The field should also be filled in case of atomic fragments.
> 
> Fixes: dbd1759e6a9c ('ipv6: on reassembly, record frag_max_size')
> Signed-off-by: Francesco Ruggeri <fruggeri@arista.com>
> 
> [...]

Here is the summary with links:
  - ipv6: record frag_max_size in atomic fragments in input path
    https://git.kernel.org/netdev/net/c/e29f011e8fc0

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