From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "linusw@kernel.org" <linusw@kernel.org>
Cc: "tony@atomide.com" <tony@atomide.com>,
"haojian.zhuang@linaro.org" <haojian.zhuang@linaro.org>,
"robh@kernel.org" <robh@kernel.org>,
"lokeshvutla@ti.com" <lokeshvutla@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nm@ti.com" <nm@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/2] pinctrl: fix group/function table leaks on consumer re-probe
Date: Wed, 4 Nov 2026 12:59:06 +0000 [thread overview]
Message-ID: <7af1eb9dd56daef2c714362160fa23873779b2d1.camel@siemens.com> (raw)
In-Reply-To: <CAD++jLn8yxh3LmUzbb2vZfJFJB=_mCZ+VeQhnZktfmuMiv5uEg@mail.gmail.com>
Hi Linus,
On Wed, 2026-11-04 at 13:30 +0100, Linus Walleij wrote:
> > Alexander Sverdlin (2):
> > pinctrl: single: don't leak group/function tables on consumer re-probe
> > pinctrl: ti-iodelay: fix memory leaks on consumer re-probe
>
> I got exactly zero reviews on this patch set from the pinctrl-single
> maintainers, so I have now just applied it.
>
> Maybe the old maintainers have other things to do, have you considered
> signing up as co-maintainer? You seem to know what you are doing.
thanks for the proposal! I will try, there is not a lot of traffic on
this driver, hopefully I'll be able to provide at least review for the
emerging patches. I'll send a patch...
--
Alexander Sverdlin
Siemens AG
www.siemens.com
prev parent reply other threads:[~2026-11-04 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 8:52 A. Sverdlin
2026-10-01 8:52 ` [PATCH 1/2] pinctrl: single: don't leak group/function tables " A. Sverdlin
2026-10-01 8:52 ` [PATCH 2/2] pinctrl: ti-iodelay: fix memory leaks " A. Sverdlin
2026-11-04 12:30 ` [PATCH 0/2] pinctrl: fix group/function table " Linus Walleij
2026-11-04 12:59 ` Sverdlin, Alexander [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=7af1eb9dd56daef2c714362160fa23873779b2d1.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=haojian.zhuang@linaro.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®