From: Johan Hovold <johan@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] sh: kfr2r09: fix i2c adapter leaks
Date: Thu, 1 Oct 2026 15:05:00 +0200 [thread overview]
Message-ID: <ar5afD7Sx-hBgTxp@hovoldconsulting.com> (raw)
In-Reply-To: <anx_ntq7VbbuQtkF@hovoldconsulting.com>
On Wed, Aug 12, 2026 at 04:13:50PM +0200, Johan Hovold wrote:
> On Sat, Jun 13, 2026 at 07:11:02AM +0200, John Paul Adrian Glaubitz wrote:
> > On Fri, 2026-06-12 at 18:00 +0200, Johan Hovold wrote:
> > > On Fri, May 08, 2026 at 02:05:59PM +0200, Johan Hovold wrote:
> > > > The kfr2r09 platform setup code fails to drop the references it acquires
> > > > to the I2C adapter.
> > >
> > > > Johan Hovold (2):
> > > > sh: kfr2r09: fix i2c adapter leak on USB gdaget setup
> > > > sh: kfr2r09: fix i2c adapter leak on serial console setup
> > >
> > > Can these be picked up now?
> >
> > I will try to review some patches this weekend.
>
> Any chance to get these into 7.3?
Can these be picked up now?
Johan
next prev parent reply other threads:[~2026-10-01 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 12:05 Johan Hovold
2026-05-08 12:06 ` [PATCH 1/2] sh: kfr2r09: fix i2c adapter leak on USB gdaget setup Johan Hovold
2026-06-24 8:29 ` Geert Uytterhoeven
2026-06-25 6:45 ` Johan Hovold
2026-05-08 12:06 ` [PATCH 2/2] sh: kfr2r09: fix i2c adapter leak on serial console setup Johan Hovold
2026-06-24 8:30 ` Geert Uytterhoeven
2026-06-12 16:00 ` [PATCH 0/2] sh: kfr2r09: fix i2c adapter leaks Johan Hovold
2026-06-13 5:11 ` John Paul Adrian Glaubitz
2026-08-12 14:13 ` Johan Hovold
2026-10-01 13:05 ` Johan Hovold [this message]
2026-10-01 16:41 ` John Paul Adrian Glaubitz
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=ar5afD7Sx-hBgTxp@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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®