All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org,
	willemdebruijn.kernel@gmail.com, shuah@kernel.org,
	sdf.kernel@gmail.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH net-next v2 0/4] net: convert UDP getsockopt to sockopt_t
Date: Thu, 02 Jul 2026 10:40:11 +0000	[thread overview]
Message-ID: <178298881139.1583217.15443135093169536299.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260630-getsockopt_phase2-v2-0-193335f3d4d1@debian.org>

Hello:

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

On Tue, 30 Jun 2026 07:01:25 -0700 you wrote:
> The leaf proto_ops getsockopt callbacks have been moving to the new
> getsockopt_iter()/sockopt_t interface.
> 
> I was trying to get SMC into getsockop and retire .getsockopt, but,
> I found the best approach is to keep converting other protocols.
> 
> This series starts the same conversion one layer down, at the struct proto
> getsockopt path, beginning with UDP.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/4] net: add sockopt_init_user() for getsockopt conversion
    https://git.kernel.org/netdev/net-next/c/b5997f911eec
  - [net-next,v2,2/4] udp: convert udp_lib_getsockopt to sockopt_t
    https://git.kernel.org/netdev/net-next/c/f99d7065a4d4
  - [net-next,v2,3/4] ipv4: raw: convert do_raw_getsockopt to sockopt_t
    https://git.kernel.org/netdev/net-next/c/9588d5da17ce
  - [net-next,v2,4/4] selftests: net: getsockopt_iter: add raw ICMP_FILTER coverage
    https://git.kernel.org/netdev/net-next/c/f4d5e3a5c7bc

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-07-02 10:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 14:01 [PATCH net-next v2 0/4] net: convert UDP getsockopt to sockopt_t Breno Leitao
2026-06-30 14:01 ` [PATCH net-next v2 1/4] net: add sockopt_init_user() for getsockopt conversion Breno Leitao
2026-06-30 18:19   ` Stanislav Fomichev
2026-07-01 21:50   ` Willem de Bruijn
2026-06-30 14:01 ` [PATCH net-next v2 2/4] udp: convert udp_lib_getsockopt to sockopt_t Breno Leitao
2026-06-30 18:20   ` Stanislav Fomichev
2026-07-01 21:51   ` Willem de Bruijn
2026-06-30 14:01 ` [PATCH net-next v2 3/4] ipv4: raw: convert do_raw_getsockopt " Breno Leitao
2026-06-30 18:20   ` Stanislav Fomichev
2026-07-01 21:52   ` Willem de Bruijn
2026-06-30 14:01 ` [PATCH net-next v2 4/4] selftests: net: getsockopt_iter: add raw ICMP_FILTER coverage Breno Leitao
2026-06-30 18:20   ` Stanislav Fomichev
2026-07-01 21:55   ` Willem de Bruijn
2026-07-02 10: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=178298881139.1583217.15443135093169536299.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf.kernel@gmail.com \
    --cc=shuah@kernel.org \
    --cc=willemdebruijn.kernel@gmail.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.