From: Breno Leitao <leitao@debian.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Robin van der Gracht <robin@protonic.nl>,
Oleksij Rempel <o.rempel@pengutronix.de>,
kernel@pengutronix.de, Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH net-next 2/2] can: isotp: convert to getsockopt_iter
Date: Tue, 4 Aug 2026 01:21:57 -0700 [thread overview]
Message-ID: <anGg-CeHzKdYvbqb@gmail.com> (raw)
In-Reply-To: <f83e25e1-b9f5-4810-bbd6-fdb8d2a10c8e@hartkopp.net>
On Wed, Jun 03, 2026 at 02:50:51PM +0200, Oliver Hartkopp wrote:
> > >
> > > Same pattern as in net/can/raw.c that had slipped in via net-next last time
> > > ;-)
> > >
> > > Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
> > >
> > > Thanks Breno!
> >
> > Thanks for the review!
> >
> > I haven't seen this on linux-next yet. Please let me know if there is any
> > update that is expected from my side.
>
> This patch will likely go upstream via can-next.
>
> Marc currently seems to be busy.
Hello, any chance that Marc is not busy anymore?
This is the last leaf nodes that is missing in this conversion now.
https://lore.kernel.org/all/20260708-getsockopt_phase3-v1-0-d8394f2fc554@debian.org/
Thanks,
--breno
prev parent reply other threads:[~2026-08-04 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 9:34 [PATCH net-next 0/2] net: convert remaining CAN protocols to getsockopt_iter Breno Leitao
2026-05-07 9:34 ` [PATCH net-next 1/2] can: j1939: convert " Breno Leitao
2026-05-11 4:21 ` Oleksij Rempel
2026-05-07 9:34 ` [PATCH net-next 2/2] can: isotp: " Breno Leitao
2026-05-11 7:05 ` Oliver Hartkopp
2026-06-03 12:25 ` Breno Leitao
2026-06-03 12:50 ` Oliver Hartkopp
2026-08-04 8:21 ` 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=anGg-CeHzKdYvbqb@gmail.com \
--to=leitao@debian.org \
--cc=kernel-team@meta.com \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=robin@protonic.nl \
--cc=socketcan@hartkopp.net \
/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