From: Jan Beulich <jbeulich@suse.com>
To: simon.marchi@polymtl.ca
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH 2/3] opcodes: fix a few -Wdiscarded-qualifiers errors
Date: Mon, 23 Feb 2026 15:27:38 +0100 [thread overview]
Message-ID: <ebc7f37c-e71a-47bc-80cf-beed3565c389@suse.com> (raw)
In-Reply-To: <20260223132805.3186869-3-simon.marchi@polymtl.ca>
On 23.02.2026 14:26, simon.marchi@polymtl.ca wrote:
> From: Simon Marchi <simon.marchi@polymtl.ca>
>
> Change-Id: Ifd43eb7ceee3bebc8be690a7fba94fc8651ffcd6
> ---
> opcodes/aarch64-dis.c | 2 +-
> opcodes/ia64-opc.c | 2 +-
> opcodes/ip2k-asm.c | 2 +-
> opcodes/riscv-dis.c | 4 ++--
> opcodes/tilegx-opc.c | 2 +-
> opcodes/tilepro-opc.c | 2 +-
> 6 files changed, 7 insertions(+), 7 deletions(-)
Okay, but please allow target maintainers (who you may have wanted to Cc) some
time to chime in. In particular ...
> --- a/opcodes/riscv-dis.c
> +++ b/opcodes/riscv-dis.c
> @@ -110,7 +110,7 @@ parse_riscv_dis_option_without_args (const char *option,
> /* Parse RISC-V disassembler option (possibly with arguments). */
>
> static void
> -parse_riscv_dis_option (const char *option, struct disassemble_info *info)
> +parse_riscv_dis_option (char *option, struct disassemble_info *info)
> {
> char *equal, *value;
>
... this change, while apparently correct, isn't very nice.
Jan
next prev parent reply other threads:[~2026-02-23 14:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 13:26 [PATCH 0/3] Fix some more " simon.marchi
2026-02-23 13:26 ` [PATCH 1/3] bfd: fix 2 " simon.marchi
2026-02-23 14:20 ` Jan Beulich
2026-02-24 15:36 ` Simon Marchi
2026-02-23 13:26 ` [PATCH 2/3] opcodes: fix a few " simon.marchi
2026-02-23 14:27 ` Jan Beulich [this message]
2026-02-24 1:14 ` Alan Modra
2026-02-24 14:58 ` Keith Seitz
2026-02-24 15:46 ` Simon Marchi
2026-02-24 17:17 ` Keith Seitz
2026-02-24 22:57 ` Alan Modra
2026-02-25 14:50 ` Keith Seitz
2026-02-23 13:26 ` [PATCH 3/3] sim: " simon.marchi
2026-02-26 18:21 ` Simon Marchi
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=ebc7f37c-e71a-47bc-80cf-beed3565c389@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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