Linux s390 Architecture development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: 3chas3@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	magnus.karlsson@intel.com, maciej.fijalkowski@intel.com,
	sdf@fomichev.me, ast@kernel.org, daniel@iogearbox.net,
	hawk@kernel.org, john.fastabend@gmail.com, jmaloy@redhat.com,
	wintera@linux.ibm.com, twinkler@linux.ibm.com,
	jchapman@katalix.com, dhowells@redhat.com,
	marc.dionne@auristor.com, david+nfc@ixit.cz,
	sameo@linux.intel.com, linux-atm-general@lists.sourceforge.net,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
	linux-s390@vger.kernel.org, linux-afs@lists.infradead.org,
	oe-linux-nfc@lists.linux.dev, kernel-team@meta.com
Subject: Re: [PATCH net-next v3 0/6] net: convert atm/xdp/af_iucv/l2tp_ppp/rxrpc/tipc to getsockopt_iter
Date: Fri, 22 May 2026 18:20:15 +0000	[thread overview]
Message-ID: <177947401569.1320830.4340885034348634311.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260520-getsock_four-v3-0-b8c0b16b7780@debian.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 20 May 2026 09:53:45 -0700 you wrote:
> This series continues the conversion of the remaining proto_ops getsockopt
> callbacks to the new getsockopt_iter callback introduced in commit 67fab22a7adc
> ("net: add getsockopt_iter callback to proto_ops").
> 
> The new callback takes a sockopt_t — a type-safe wrapper around iov_iter
> plus an optlen field — instead of raw __user pointers. This:
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/6] af_iucv: convert to getsockopt_iter
    https://git.kernel.org/netdev/net-next/c/347fdd4df85f
  - [net-next,v3,2/6] atm: convert to getsockopt_iter
    https://git.kernel.org/netdev/net-next/c/4177767daf83
  - [net-next,v3,3/6] xdp: convert to getsockopt_iter
    https://git.kernel.org/netdev/net-next/c/3c6776b5b912
  - [net-next,v3,4/6] l2tp: ppp: convert to getsockopt_iter
    https://git.kernel.org/netdev/net-next/c/f83e9cd64593
  - [net-next,v3,5/6] rxrpc: convert to getsockopt_iter
    https://git.kernel.org/netdev/net-next/c/4b94edae0b6c
  - [net-next,v3,6/6] tipc: convert to getsockopt_iter
    https://git.kernel.org/netdev/net-next/c/c56dbb469fe2

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-05-22 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 16:53 [PATCH net-next v3 0/6] net: convert atm/xdp/af_iucv/l2tp_ppp/rxrpc/tipc to getsockopt_iter Breno Leitao
2026-05-20 16:53 ` [PATCH net-next v3 1/6] af_iucv: convert " Breno Leitao
2026-05-20 16:53 ` [PATCH net-next v3 2/6] atm: " Breno Leitao
2026-05-20 16:53 ` [PATCH net-next v3 3/6] xdp: " Breno Leitao
2026-05-20 16:53 ` [PATCH net-next v3 4/6] l2tp: ppp: " Breno Leitao
2026-05-20 16:53 ` [PATCH net-next v3 5/6] rxrpc: " Breno Leitao
2026-05-20 16:53 ` [PATCH net-next v3 6/6] tipc: " Breno Leitao
2026-05-22 18:20 ` 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=177947401569.1320830.4340885034348634311.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=3chas3@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=david+nfc@ixit.cz \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=jchapman@katalix.com \
    --cc=jmaloy@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=marc.dionne@auristor.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-linux-nfc@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=sameo@linux.intel.com \
    --cc=sdf@fomichev.me \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=twinkler@linux.ibm.com \
    --cc=wintera@linux.ibm.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