From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Hans de Goede <hansg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Kenneth Chan <kenneth.t.chan@gmail.com>,
platform-driver-x86@vger.kernel.org,
Azael Avalos <coproscefalo@gmail.com>,
Matthew Garrett <matthew.garrett@nebula.com>
Subject: Re: [PATCH v1 0/2] platform/x86: Fixes for leaks in panasonic-laptop and toshiba-haps drivers
Date: Tue, 27 Jan 2026 13:04:43 +0200 (EET) [thread overview]
Message-ID: <19b87b6d-2d9b-8662-8580-e883943aa264@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0gY9O0A-UNtsA7YJ7Za85sDA3qFpe-phjhE_4cZ4HP4YQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]
On Mon, 26 Jan 2026, Rafael J. Wysocki wrote:
> On Mon, Jan 26, 2026 at 3:56 PM Ilpo Järvinen
> <ilpo.jarvinen@linux.intel.com> wrote:
> >
> > On Tue, 20 Jan 2026 16:42:41 +0100, Rafael J. Wysocki wrote:
> >
> > > These are two fixes for leaks in the panasonic-laptop and toshiba-haps drivers,
> > > in the "probe error" and "remove" paths.
> > >
> > > Thanks!
> > >
> >
> >
> > Thank you for your contribution, it has been applied to my local
> > review-ilpo-fixes branch. Note it will show up in the public
> > platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
> > local branch there, which might take a while.
> >
> > The list of commits applied:
> > [1/2] platform/x86: panasonic-laptop: Fix sysfs group leak in error path
> > commit: 43b0b7eff4b3fb684f257d5a24376782e9663465
> > [2/2] platform/x86: toshiba_haps: Fix memory leaks in add/remove routines
> > commit: 128497456756e1b952bd5a912cd073836465109d
>
> Thanks!
>
> Just to confirm, I sent a v2 of the second patch in the meantime:
>
> https://lore.kernel.org/linux-acpi/12823935.O9o76ZdvQC@rafael.j.wysocki/
>
> I gather that this is what you have applied. In any case, it is a
> replacement for the v1.
Yes, I used the devm_ variant of patch 2 (v2). ...Had to jump through
a few hoops though to get b4 to apply things correctly, and this is what
you get as a confirmation/thankyou email if you don't refresh the whole
series but just a single patch in it.
--
i.
next prev parent reply other threads:[~2026-01-27 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 15:42 [PATCH v1 0/2] platform/x86: Fixes for leaks in panasonic-laptop and toshiba-haps drivers Rafael J. Wysocki
2026-01-20 15:43 ` [PATCH v1 1/2] platform/x86: panasonic-laptop: Fix sysfs group leak in error path Rafael J. Wysocki
2026-01-20 15:44 ` [PATCH v1 2/2] platform/x86: toshiba_haps: Fix memory leaks in add/remove routines Rafael J. Wysocki
2026-01-21 10:57 ` [PATCH v2 " Rafael J. Wysocki
2026-01-26 14:56 ` [PATCH v1 0/2] platform/x86: Fixes for leaks in panasonic-laptop and toshiba-haps drivers Ilpo Järvinen
2026-01-26 19:00 ` Rafael J. Wysocki
2026-01-27 11:04 ` Ilpo Järvinen [this message]
2026-01-27 13:36 ` Rafael J. Wysocki
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=19b87b6d-2d9b-8662-8580-e883943aa264@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=coproscefalo@gmail.com \
--cc=hansg@kernel.org \
--cc=kenneth.t.chan@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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