From: Lee Jones <lee@kernel.org>
To: lee@kernel.org, krzk@kernel.org, alim.akhtar@samsung.com,
s.nawrocki@samsung.com, m.szyprowski@samsung.com,
ideal.song@samsung.com, beomho.seo@samsung.com,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2 0/3] mfd: exynos-lpass: Fix some error handling paths
Date: Thu, 01 May 2025 12:18:04 +0100 [thread overview]
Message-ID: <174609828442.3756623.12093382132101705631.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1745247209.git.christophe.jaillet@wanadoo.fr>
On Mon, 21 Apr 2025 17:00:32 +0200, Christophe JAILLET wrote:
> This serie fixes several issues related to error handling paths in
> drivers/mfd/exynos-lpass.c.
>
> I've split it in 3 patches to ease review, but it could be merge in only
> 1 patch if preferred.
>
> Patch 1: Fix a leak in the error handling path of the probe. It should
> be straighforward. This patch is already R-b.
>
> [...]
Applied, thanks!
[1/3] mfd: exynos-lpass: Fix an error handling path in exynos_lpass_probe()
commit: 8cc4952d1e8618eff474dc7154c6537db88178df
[2/3] mfd: exynos-lpass: Avoid calling exynos_lpass_disable() twice in exynos_lpass_remove()
commit: cb931849ec1e71900eb54d0a377ae30e0bcfcffa
[3/3] mfd: exynos-lpass: Fix another error handling path in exynos_lpass_probe()
commit: f408e20757afa3d8c719a8a804cd2c83262514dd
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-05-01 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 15:00 Christophe JAILLET
2025-04-21 15:00 ` [PATCH v2 1/3] mfd: exynos-lpass: Fix an error handling path in exynos_lpass_probe() Christophe JAILLET
2025-04-21 15:00 ` [PATCH v2 2/3] mfd: exynos-lpass: Avoid calling exynos_lpass_disable() twice in exynos_lpass_remove() Christophe JAILLET
2025-04-21 15:00 ` [PATCH v2 3/3] mfd: exynos-lpass: Fix another error handling path in exynos_lpass_probe() Christophe JAILLET
2025-04-23 16:33 ` Krzysztof Kozlowski
2025-05-01 11:18 ` Lee Jones [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=174609828442.3756623.12093382132101705631.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=beomho.seo@samsung.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=ideal.song@samsung.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=s.nawrocki@samsung.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®