From: Leo Yan <leo.yan@arm.com>
To: Markus Elfring <Markus.Elfring@web.de>,
linux-perf-users@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
Ian Rogers <irogers@google.com>, Ingo Molnar <mingo@redhat.com>,
James Clark <james.clark@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf maps: Process kcore maps in order
Date: Thu, 9 May 2024 15:46:28 +0100 [thread overview]
Message-ID: <438f8725-ef3f-462f-90e2-840cab478ee5@arm.com> (raw)
In-Reply-To: <4294f69b-a317-4f09-b775-52439e2ea6fc@web.de>
On 5/8/2024 6:02 PM, Markus Elfring wrote:
>> … To fix it, this
>> patch adds kcore maps in the tail of list, …
>
> * How do you think about to add the tag “Fixes”?
>
> * Would you like to use imperative wordings for an improved changelog?
I will add Fixes tag and refine changelog. Thanks for suggestions.
Leo
prev parent reply other threads:[~2024-05-09 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240505202805.583253-1-leo.yan@arm.com>
2024-05-08 17:02 ` [PATCH] perf maps: Process kcore maps in order Markus Elfring
2024-05-09 14:46 ` Leo Yan [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=438f8725-ef3f-462f-90e2-840cab478ee5@arm.com \
--to=leo.yan@arm.com \
--cc=Markus.Elfring@web.de \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).