From: Steve Clevenger <scclevenger@os.amperecomputing.com>
To: Leo Yan <leo.yan@arm.com>, james.clark@linaro.org, mike.leach@linaro.org
Cc: suzuki.poulose@arm.com, ilkka@os.amperecomputing.com,
coresight@lists.linaro.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V5 0/4] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset
Date: Thu, 29 Aug 2024 10:39:34 -0700 [thread overview]
Message-ID: <01419593-056b-41e9-a3d2-6ac490f7734a@os.amperecomputing.com> (raw)
In-Reply-To: <35c19a0f-580a-4d97-b0d4-b8708a4dbdb4@arm.com>
On 8/29/2024 12:55 AM, Leo Yan wrote:
> On 8/29/2024 12:17 AM, Steve Clevenger wrote:
>>
>> Changes in V5:
>> - In symbol-elf.c, branch to exit_close label if open file.
>> - In trace_event_python.c, correct indentation. set_sym_in_dict
>> call parameter "map_pgoff" renamed as "addr_map_pgoff" to
>> match local naming.
>
> For the series:
>
> Reviewed-by: Leo Yan <leo.yan@arm.com>
>
> Hi Steve,
>
> Later when you respin a new version patches, it is better to amend the review
> and ACK tags you have received. (Just remind, b4 is your friend for helping do
> these things).
>
> Thanks,
> Leo
Got it. Thanks, Leo. By the way, I noticed when I rebased to
perf-tools-next the kernel version was 6.11-rc3. Is there any chance
this patch gets into 6.11?
Steve
next prev parent reply other threads:[~2024-08-29 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 23:17 [PATCH V5 0/4] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset Steve Clevenger
2024-08-28 23:17 ` PATCH V5 4/4] Adjust objdump start/end range per map pgoff parameter Steve Clevenger
2024-08-28 23:17 ` [PATCH V5 3/4] Add map pgoff to python dictionary based on MAPPING_TYPE Steve Clevenger
2024-08-28 23:17 ` [PATCH V5 2/4] Force MAPPING_TYPE__IDENTIY for PIE Steve Clevenger
2024-08-28 23:17 ` PATCH V5 1/4] Add dso__is_pie call to identify ELF PIE Steve Clevenger
2024-08-29 7:55 ` [PATCH V5 0/4] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset Leo Yan
2024-08-29 17:39 ` Steve Clevenger [this message]
2024-08-30 7:20 ` Leo Yan
2024-08-31 19:19 ` Steve Clevenger
2024-09-01 13:53 ` Leo Yan
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=01419593-056b-41e9-a3d2-6ac490f7734a@os.amperecomputing.com \
--to=scclevenger@os.amperecomputing.com \
--cc=coresight@lists.linaro.org \
--cc=ilkka@os.amperecomputing.com \
--cc=james.clark@linaro.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).