public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Ying Huang" <ying.huang@oss.cipunited.com>
To: "Nick Clifton" <nickc@redhat.com>, <binutils@sourceware.org>
Cc: <yunqiang.su@oss.cipunited.com>
Subject: Re: [PATCH v2] MIPS: Change all E_MIPS_* to EF_MIPS_*
Date: Mon, 13 Nov 2023 11:21:58 +0800	[thread overview]
Message-ID: <17db8e54-1651-4ad0-b7de-7846211935d4@oss.cipunited.com> (raw)
In-Reply-To: <c9017326-8778-4d43-a728-01ecc5555cde@redhat.com>

Hi Nick,

在 2023/11/10 22:12, Nick Clifton 写道:
> Hi Ying Huang,
>
>> Ping,
>
> Sorry for the delay in reviewing your patch.
>
>
>>> Now MIPS has two macro definitions for ELF file header flags,
>>> respectively E_ and EF_. It is difficult to decide which style macro
>>> we should use when we want to add new ELF file header flags.
>>>
>>> We can refer to this message coming from the lost world:
>>> .
>>> Clearly IRIX and the Linux kernel used to use EF_* macros.
>>> So we should use EF_* to keep same style with the beginning.
>
> I agree that having inconsistent naming schemes for the macros
> is annoying.  But I dislike the idea of a backwards incompatible
> change.  It is not only the binutils, gdb and glibc that use these
> macros but other programs as well.
>
> To that end I have amended your patch so that the changes to
> include/elf/mips.h and elfcpp/mips.h also keep the old definitions
> of the constants.  This means that other users of these files
> will not have to change their code unless they want to.
>
Yes, your consideration is very comprehensive.


>
> >> And we also have submitted this change to glibc.
>
> You will also need to submit the changes to gdb/mips-tdep.c
> and sim/mips/interp.c to the gdb mailing list as these files
> are not maintained by the Binutils project.
>
>
OK. I would send to gdb later.
>>> bfd/elf32-mips.c | 4 +-
>>> bfd/elfxx-mips.c | 224 +++++++++++++++++++++----------------------
>>> binutils/readelf.c | 76 +++++++--------
>>> elfcpp/mips.h | 74 +++++++-------
>>> gas/config.in | 6 +-
>>> gas/config/tc-mips.c | 10 +-
>>> gas/configure | 8 +-
>>> gas/configure.ac | 10 +-
>>> gold/mips.cc | 168 ++++++++++++++++----------------
>>> include/elf/mips.h | 74 +++++++-------
>
> Approved and applied - with the change mentioned above.
>
> One other thing - your email program appears to have mangled
> the patch, removing lots of whitespace.  This made the patch
> impossible to apply automatically and instead I had to apply
> it by hand.  In the future, please could you supply the patch
> as an attachment, rather than inline ?
>
> Cheers
>   Nick
>
>
I checked the email sourcecode of "[PATCH v2] MIPS: Change all E_MIPS_* to EF_MIPS_*" , and found that there have two types of contents, including text diff and html diff.

And I try to submit it again using 'git send-email', this problem did not occur again.

Next time I would checked again.

Thanks!

Ying

      reply	other threads:[~2023-11-13  3:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  6:36 Ying Huang
2023-11-01  6:29 ` Ying Huang
2023-11-10 14:12   ` Nick Clifton
2023-11-13  3:21     ` Ying Huang [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=17db8e54-1651-4ad0-b7de-7846211935d4@oss.cipunited.com \
    --to=ying.huang@oss.cipunited.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    --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).