From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>,
<coresight@lists.linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
James Clark <james.clark@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Mike Leach <mike.leach@linaro.org>,
Suzuki Poulouse <suzuki.poulose@arm.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] coresight: trbe: Fix return value check in arm_trbe_register_coresight_cpu()
Date: Tue, 22 Oct 2024 11:00:35 +0800 [thread overview]
Message-ID: <98933782-5e39-1cd8-8a1c-a7c2320e19d1@huawei.com> (raw)
In-Reply-To: <d693331d-1e86-415f-8fdc-6a6b43f110a5@web.de>
On 2024/10/21 18:25, Markus Elfring wrote:
> …
>> memory instead of coresight_get_platform_data(), but forgot to update the
>> return value check code accordingly. Fix the incorrect return value check
>> for devm_kzalloc(), which returns NULL instead of ERR_PTR() when it fails.
> …
>> ---
>> drivers/hwtracing/coresight/coresight-trbe.c | 2 +-
> …
>
> It would have been nice to add a patch version description.
Yes, I forgot the description, thanks. Only the commit message is updated in v2,
especially Fixes. But I'm not going to post v3.
>
> See also:
> * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc4#n321
>
> * https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22
>
>
> Regards,
> Markus
> .
>
--
Regards,
Zhen Lei
prev parent reply other threads:[~2024-10-22 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 7:21 [PATCH v2 1/1] " Zhen Lei
2024-10-21 10:25 ` [PATCH v2] " Markus Elfring
2024-10-22 3:00 ` Leizhen (ThunderTown) [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=98933782-5e39-1cd8-8a1c-a7c2320e19d1@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=Markus.Elfring@web.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@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
all inboxes | Powered by JetHome®