From: Krzysztof Kozlowski <krzk@kernel.org>
To: Liao Yuanhong <liaoyuanhong@vivo.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
"open list:MAILBOX ARM MHUv3" <linux-kernel@vger.kernel.org>,
"moderated list:MAILBOX ARM MHUv3"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] mailbox: arm_mhuv3: Remove no_free_ptr() to maintain the original form of the pointer
Date: Mon, 11 Aug 2025 13:01:37 +0200 [thread overview]
Message-ID: <d4432510-9691-4b6e-8733-afe9e737eecb@kernel.org> (raw)
In-Reply-To: <20250811082536.377896-1-liaoyuanhong@vivo.com>
On 11/08/2025 10:25, Liao Yuanhong wrote:
> Remove no_free_ptr() to ensure PTR_ERR() consistently retrieves the correct
> error code.
Fixes tag?
Also, your commit msg does not look like wrapped according to submitting
rules.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-08-11 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 8:25 [PATCH] mailbox: arm_mhuv3: Remove no_free_ptr() to maintain the original form of the pointer Liao Yuanhong
2025-08-11 9:30 ` Cristian Marussi
2025-08-11 11:01 ` Krzysztof Kozlowski [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=d4432510-9691-4b6e-8733-afe9e737eecb@kernel.org \
--to=krzk@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=jassisinghbrar@gmail.com \
--cc=liaoyuanhong@vivo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@arm.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