From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Johan Hovold <johan@kernel.org>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] MIPS: ip22-gio: fix leaks and replace static root
Date: Wed, 27 May 2026 10:06:21 +0200 [thread overview]
Message-ID: <ahal_RNl6ACvPEVf@alpha.franken.de> (raw)
In-Reply-To: <20260424102849.2616035-1-johan@kernel.org>
On Fri, Apr 24, 2026 at 12:28:44PM +0200, Johan Hovold wrote:
> This series fixes some issues found through inspection when looking into
> replacing the statically allocated gio bus root device.
>
> Johan
>
>
> Johan Hovold (5):
> MIPS: ip22-gio: fix kfree() of static object
> MIPS: ip22-gio: fix gio device memory leak
> MIPS: ip22-gio: fix device reference leak in probe
> MIPS: ip22-gio: switch to dynamic root device
> MIPS: ip22-gio: do not export device release function
>
> arch/mips/include/asm/gio_device.h | 6 ------
> arch/mips/sgi-ip22/ip22-gio.c | 34 ++++++++++--------------------
> 2 files changed, 11 insertions(+), 29 deletions(-)
series applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2026-05-27 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 10:28 [PATCH 0/5] MIPS: ip22-gio: fix leaks and replace static root Johan Hovold
2026-04-24 10:28 ` [PATCH 1/5] MIPS: ip22-gio: fix kfree() of static object Johan Hovold
2026-04-24 10:28 ` [PATCH 2/5] MIPS: ip22-gio: fix gio device memory leak Johan Hovold
2026-04-24 10:28 ` [PATCH 3/5] MIPS: ip22-gio: fix device reference leak in probe Johan Hovold
2026-04-24 10:28 ` [PATCH 4/5] MIPS: ip22-gio: switch to dynamic root device Johan Hovold
2026-04-24 10:28 ` [PATCH 5/5] MIPS: ip22-gio: do not export device release function Johan Hovold
2026-05-27 8:06 ` Thomas Bogendoerfer [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=ahal_RNl6ACvPEVf@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox