From: Breno Leitao <leitao@debian.org>
To: David Heidelberg <david@ixit.cz>
Cc: "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>,
oe-linux-nfc@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, sdf.kernel@gmail.com,
kernel-team@meta.com
Subject: Re: [PATCH net-next 0/2] nfc: llcp: Move to .getsockopt_iter
Date: Wed, 12 Aug 2026 03:25:38 -0700 [thread overview]
Message-ID: <anxJuZZ7w2x7tkBr@gmail.com> (raw)
In-Reply-To: <8536d413-a46c-4798-8feb-d4a0e0fa78c2@ixit.cz>
Hello David,
On Tue, Aug 11, 2026 at 08:46:11PM +0200, David Heidelberg wrote:
> On 30/07/2026 15:07, Breno Leitao wrote:
> > On Wed, Jul 08, 2026 at 04:51:57AM -0700, Breno Leitao wrote:
> > > Continue to convert the protocols to getsockopt_iter callback.
> >
> > Hello David,
> >
> > Have you had a chance to look at this change?
>
> Hello Breno,
>
> sadly I don't have it inside my mailbox nor archive.
No worries, I see it in lore:
https://lore.kernel.org/all/20260708-getsockopt_phase3-v1-0-d8394f2fc554@debian.org/
> Can you send it again please?
Sure, I am happy to resend.
> Preferably in a week after another batch of fixes will land?
Sorry, what fixes are those?
Thanks
--breno
prev parent reply other threads:[~2026-08-12 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 11:51 [PATCH net-next 0/2] nfc: llcp: Move to .getsockopt_iter Breno Leitao
2026-07-08 11:51 ` [PATCH net-next 1/2] nfc: llcp: widen getsockopt value locals to u32 Breno Leitao
2026-07-08 11:51 ` [PATCH net-next 2/2] nfc: llcp: convert to getsockopt_iter Breno Leitao
2026-07-30 13:07 ` [PATCH net-next 0/2] nfc: llcp: Move to .getsockopt_iter Breno Leitao
2026-08-11 18:46 ` David Heidelberg
2026-08-12 10:25 ` Breno Leitao [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=anxJuZZ7w2x7tkBr@gmail.com \
--to=leitao@debian.org \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sdf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox