From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Junhao He <hejunhao3@huawei.com>
Cc: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<namhyung@kernel.org>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>, <jolsa@kernel.org>,
<irogers@google.com>, <james.clark@linaro.org>, <leo.yan@arm.com>,
<john.g.garry@oracle.com>, <will@kernel.org>,
<mike.leach@linaro.org>, <yangyicong@hisilicon.com>,
<linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/3] perf vendor events arm64: Drop hip08 PublicDescription if same as BriefDescription
Date: Fri, 25 Apr 2025 12:08:52 +0100 [thread overview]
Message-ID: <20250425120852.000073a4@huawei.com> (raw)
In-Reply-To: <20250418070812.3771441-3-hejunhao3@huawei.com>
On Fri, 18 Apr 2025 15:08:11 +0800
Junhao He <hejunhao3@huawei.com> wrote:
> If BriefDescription and PublicDescription are the same, only
> BriefDescription is needed. It will be used for both long and
> short format outputs.
>
> Signed-off-by: Junhao He <hejunhao3@huawei.com>
LGTM
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
next prev parent reply other threads:[~2025-04-25 12:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 7:08 [PATCH v2 0/3] perf vendor events arm64: Do some cleanup for Hisi hip08 json Junhao He
2025-04-18 7:08 ` [PATCH v2 1/3] perf vendor events arm64: Fill up Desc field for Hisi hip08 hha pmu Junhao He
2025-04-22 7:14 ` Yicong Yang
2025-04-25 11:06 ` Jonathan Cameron
2025-04-25 14:31 ` Arnaldo Carvalho de Melo
2025-04-18 7:08 ` [PATCH v2 2/3] perf vendor events arm64: Drop hip08 PublicDescription if same as BriefDescription Junhao He
2025-04-22 7:15 ` Yicong Yang
2025-04-25 11:08 ` Jonathan Cameron [this message]
2025-04-18 7:08 ` [PATCH v2 3/3] MAINTAINERS: Add hisilicon pmu json events under its entry Junhao He
2025-04-22 7:15 ` Yicong Yang
2025-04-25 11:09 ` Jonathan Cameron
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=20250425120852.000073a4@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=hejunhao3@huawei.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.