From: Breno Leitao <leitao@debian.org>
To: Adam Young <admiyo@amperemail.onmicrosoft.com>
Cc: Jeremy Kerr <jk@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
Martin Schiller <ms@dev.tdt.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Shuah Khan <shuah@kernel.org>,
linux-x25@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH net-next v2 1/5] mctp: convert to getsockopt_iter
Date: Fri, 8 May 2026 01:21:28 -0700 [thread overview]
Message-ID: <af2ceIWaM4K6vDNS@gmail.com> (raw)
In-Reply-To: <9b8f8cbd-9b94-47f0-a4af-713060d9aef1@amperemail.onmicrosoft.com>
Hello Adam,
On Thu, May 07, 2026 at 04:10:36PM -0400, Adam Young wrote:
> Why is this 1/5 and where are the other 4?
The entire series was sent as one submission, and I've verified that all
recipients received the complete patchset. Did you not receive the other
patches?
You can find the full patchset here on lore:
https://lore.kernel.org/all/20260507-getsock_two-v2-0-5873111d9c12@debian.org/
next prev parent reply other threads:[~2026-05-08 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 10:57 [PATCH net-next v2 0/5] net: convert four more protocols to getsockopt_iter Breno Leitao
2026-05-07 10:57 ` [PATCH net-next v2 1/5] mctp: convert " Breno Leitao
2026-05-07 20:10 ` Adam Young
2026-05-08 8:21 ` Breno Leitao [this message]
2026-05-07 10:57 ` [PATCH net-next v2 2/5] llc: " Breno Leitao
2026-05-07 10:57 ` [PATCH net-next v2 3/5] x25: " Breno Leitao
2026-05-07 10:57 ` [PATCH net-next v2 4/5] kcm: " Breno Leitao
2026-05-07 10:57 ` [PATCH net-next v2 5/5] selftests: net: getsockopt_iter: cleanup Breno Leitao
2026-05-10 17:20 ` [PATCH net-next v2 0/5] net: convert four more protocols to getsockopt_iter patchwork-bot+netdevbpf
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=af2ceIWaM4K6vDNS@gmail.com \
--to=leitao@debian.org \
--cc=admiyo@amperemail.onmicrosoft.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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