From: "Ying Huang" <ying.huang@oss.cipunited.com>
To: <gdb-patches@sourceware.org>
Cc: <yunqiang.su@oss.cipunited.com>
Subject: [PATCH 0/2] Change all E_MIPS_* to EF_MIPS_*
Date: Tue, 14 Nov 2023 17:45:33 +0800 [thread overview]
Message-ID: <20231114094535.434194-1-ying.huang@oss.cipunited.com> (raw)
According to we have changed all E_MIPS_* to EF_MIPS_* in binutils
and glibc, we also need to change it here to keep same style.
We can refer to this commit record:
https://sourceware.org/pipermail/binutils/2023-October/129904.html
next reply other threads:[~2023-11-14 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 9:45 Ying Huang [this message]
2023-11-14 9:45 ` [PATCH 1/2] gdb: mips: Change " Ying Huang
2023-11-14 9:45 ` [PATCH 2/2] sim: " Ying Huang
2023-11-14 11:43 ` [PATCH 0/2] Change all " Pedro Alves
2023-11-15 2:19 ` Ying Huang
2023-11-16 2:25 ` YunQiang Su
2023-11-15 2:30 Ying Huang
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=20231114094535.434194-1-ying.huang@oss.cipunited.com \
--to=ying.huang@oss.cipunited.com \
--cc=gdb-patches@sourceware.org \
--cc=yunqiang.su@oss.cipunited.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 read-only IMAP folder(s) and NNTP newsgroup(s).