public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Ying Huang <ying.huang@oss.cipunited.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v11 2/3] MIPS: Add new section type SHT_MIPS_ABIFLAGS
Date: Thu, 21 Sep 2023 08:49:35 +0200	[thread overview]
Message-ID: <c454ecdf-64ee-4408-b9ef-863bb7dc744e@linaro.org> (raw)
In-Reply-To: <20230831032302.3736352-3-ying.huang@oss.cipunited.com>

Ok, it syncs with binutils commit 351cdf24d223290b15fa991e5052ec9e9bd1e284.

On 31/08/23 00:22, Ying Huang wrote:
> From: Ying Huang <ying.huang@oss.cipunited.com>
> 
> ---
>  elf/elf.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/elf/elf.h b/elf/elf.h
> index 43657f6b46..1417cfd83f 100644
> --- a/elf/elf.h
> +++ b/elf/elf.h
> @@ -1809,6 +1809,7 @@ typedef struct
>  #define SHT_MIPS_EH_REGION	0x70000027
>  #define SHT_MIPS_XLATE_OLD	0x70000028
>  #define SHT_MIPS_PDR_EXCEPTION	0x70000029
> +#define SHT_MIPS_ABIFLAGS	0x7000002a
>  #define SHT_MIPS_XHASH		0x7000002b
>  
>  /* Legal values for sh_flags field of Elf32_Shdr.  */

  reply	other threads:[~2023-09-21  6:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  3:22 [PATCH v11 0/3] MIPS: Sync elf.h from binutils Ying Huang
2023-08-31  3:22 ` [PATCH v11 1/3] MIPS: Add ELF file header flags Ying Huang
2023-09-11  6:27   ` Ying Huang
2023-09-21  6:03     ` Ying Huang
2023-09-21  6:47   ` Adhemerval Zanella Netto
2023-09-22  2:52     ` Ying Huang
2023-09-27 13:42       ` Adhemerval Zanella Netto
2023-08-31  3:22 ` [PATCH v11 2/3] MIPS: Add new section type SHT_MIPS_ABIFLAGS Ying Huang
2023-09-21  6:49   ` Adhemerval Zanella Netto [this message]
2023-08-31  3:22 ` [PATCH v11 3/3] MIPS: Add relocation types Ying Huang
2023-09-21  6:50   ` Adhemerval Zanella Netto

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=c454ecdf-64ee-4408-b9ef-863bb7dc744e@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=ying.huang@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).