From: WANG Xuerui <i.swmail@xen0n.name>
To: liuzhensong <liuzhensong@loongson.cn>,
WANG Xuerui <i.swmail@xen0n.name>,
binutils@sourceware.org
Cc: Chenghua Xu <xuchenghua@loongson.cn>,
Xi Ruoyao <xry111@xry111.site>, WANG Xuerui <git@xen0n.name>
Subject: Re: [PATCH 1/2] opcodes/loongarch: Remove unused code
Date: Tue, 2 Aug 2022 15:11:47 +0800 [thread overview]
Message-ID: <d24ae611-4d8e-289b-c65b-e8c88e991bc7@xen0n.name> (raw)
In-Reply-To: <84b313da-3783-9d2c-7518-86cf6ea7f7ea@loongson.cn>
On 2022/8/2 15:02, liuzhensong wrote:
>
>
> 在 2022/8/1 下午3:07, WANG Xuerui 写道:
>> On 2022/7/19 11:03, WANG Xuerui wrote:
>>> From: WANG Xuerui <git@xen0n.name>
>>>
>>> include/ChangeLog
>>> * opcode/loongarch.h (loongarch_parse_dis_options): Remove
>>> unused declarations.
>>> (loongarch_disassemble_one): Likewise.
>>>
>>> opcodes/ChangeLog
>>> * loongarch-dis.c (loongarch_parse_dis_options): Remove
>>> unused code.
>>> (my_print_address_func): Likewise.
>>> (loongarch_disassemble_one): Likewise.
>>>
>>> Signed-off-by: WANG Xuerui <git@xen0n.name>
>>> ---
>>> include/ChangeLog | 6 ++++++
>>> include/opcode/loongarch.h | 5 -----
>>> opcodes/ChangeLog | 7 +++++++
>>> opcodes/loongarch-dis.c | 35 -----------------------------------
>>> 4 files changed, 13 insertions(+), 40 deletions(-)
>>
>> A gentle ping for this patchset.
>
> This patchsethas been verified that there is no problem but cannot be
> directly patched.
Do you mean I should rebase it by "cannot be directly patched"? Or is
there any other places that I have missed (e.g. testsuite)?
next prev parent reply other threads:[~2022-08-02 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 3:03 WANG Xuerui
2022-07-19 3:03 ` [PATCH 2/2] opcodes/loongarch: Implement style support in the disassembler WANG Xuerui
2022-08-01 7:07 ` [PATCH 1/2] opcodes/loongarch: Remove unused code WANG Xuerui
2022-08-02 7:02 ` liuzhensong
2022-08-02 7:11 ` WANG Xuerui [this message]
2022-08-02 7:33 ` liuzhensong
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=d24ae611-4d8e-289b-c65b-e8c88e991bc7@xen0n.name \
--to=i.swmail@xen0n.name \
--cc=binutils@sourceware.org \
--cc=git@xen0n.name \
--cc=liuzhensong@loongson.cn \
--cc=xry111@xry111.site \
--cc=xuchenghua@loongson.cn \
/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).