From: Breno Leitao <leitao@debian.org>
To: Emanuele Ghidoli <ghidoliemanuele@gmail.com>
Cc: stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org,
regressions@lists.linux.dev,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
Subject: Re: [PATCH 6.12.y] net: call getsockopt_iter if available
Date: Mon, 26 Oct 2026 03:09:16 -0700 [thread overview]
Message-ID: <at8mjBKGXLd9JHaX@gmail.com> (raw)
In-Reply-To: <20261022111535.528099-1-ghidoliemanuele@gmail.com>
On Thu, Oct 22, 2026 at 01:15:21PM +0200, Emanuele Ghidoli wrote:
>
> v6.12.114 picked up commit 41fbf726915b ("net: add getsockopt_iter
> callback to proto_ops", upstream 67fab22a7adc) and commit 22ebe6ab0b67
> ("Bluetooth: L2CAP: convert to getsockopt_iter", upstream bf01627cc04b)
> as dependencies of commit 3af72bf8f73c ("Bluetooth: L2CAP: access
> chan->conn safely in get/setsockopt", upstream ca2c4c264986), but not
> this patch, which is the one making do_sock_getsockopt() actually call
> ->getsockopt_iter().
Right, if you got the protocol's conversion to getsockopt iterator, you
need this one as well.
prev parent reply other threads:[~2026-10-26 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 11:15 [PATCH 6.12.y] net: call getsockopt_iter if available Emanuele Ghidoli
2026-10-22 12:39 ` [6.12.y] " bluez.test.bot
2026-10-23 20:02 ` [PATCH 6.12.y] " Sasha Levin
2026-10-26 10:09 ` 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=at8mjBKGXLd9JHaX@gmail.com \
--to=leitao@debian.org \
--cc=emanuele.ghidoli@toradex.com \
--cc=ghidoliemanuele@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=sdf@fomichev.me \
--cc=stable@vger.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 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.