public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Justin Iurman <justin.iurman@uliege.be>
Cc: netdev@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] ioam6: fix write to cloned skb's
Date: Thu, 22 Feb 2024 08:40:27 +0000	[thread overview]
Message-ID: <170859122751.10907.15669558158966049047.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240219135255.15429-1-justin.iurman@uliege.be>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Mon, 19 Feb 2024 14:52:53 +0100 you wrote:
> v3:
>  - fix patches tag ("net" and version were removed unexpectedly)
> 
> v2:
>  - use skb_ensure_writable() instead of skb_cloned()+pskb_expand_head()
>  - refresh network header pointer in ip6_parse_tlv() when returning from
>    ipv6_hop_ioam()
> 
> [...]

Here is the summary with links:
  - [net,v3,1/2] Fix write to cloned skb in ipv6_hop_ioam()
    https://git.kernel.org/netdev/net/c/f198d933c2e4
  - [net,v3,2/2] selftests: ioam: refactoring to align with the fix
    https://git.kernel.org/netdev/net/c/187bbb6968af

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-22  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 13:52 [PATCH net v3 0/2] ioam6: fix write to cloned skb's Justin Iurman
2024-02-19 13:52 ` [PATCH net v3 1/2] Fix write to cloned skb in ipv6_hop_ioam() Justin Iurman
2024-02-19 13:52 ` [PATCH net v3 2/2] selftests: ioam: refactoring to align with the fix Justin Iurman
2024-02-22  8:40 ` 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=170859122751.10907.15669558158966049047.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=justin.iurman@uliege.be \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox