public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: YunQiang Su <wzssyqa@gmail.com>
To: Nick Clifton <nickc@redhat.com>, Matthias Klose <doko@debian.org>
Cc: binutils@sourceware.org, YunQiang Su <yunqiang.su@cipunited.com>
Subject: Re: [PATCH v5 0/4] Gold/MIPS: Improve MIPS support in configure.tgt
Date: Mon, 13 Nov 2023 13:11:05 +0800	[thread overview]
Message-ID: <CAKcpw6X3vZ1Of9nNvQDKtCRYpzva8kSf7T-1T-nkOuU3TVA5Tw@mail.gmail.com> (raw)
In-Reply-To: <20231113050549.702494-1-yunqiang.su@cipunited.com>

YunQiang Su <yunqiang.su@cipunited.com> 于2023年11月13日周一 13:06写道:
>
> YunQiang Su (4):
>   Gold: Add targ_extra_little_endian to configure.ac
>   Gold/MIPS: Drop mips*le/mips*el* triple pattern
>   Gold/MIPS: Add targ_extra_size=64 for mips32 triples
>   Gold/MIPS: Add mips64*/mips64*el triple support
>

If this patchset is OK, can/should we backport this patchset to 2.41?
We meet this problem:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050431

      parent reply	other threads:[~2023-11-13  5:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13  5:05 YunQiang Su
2023-11-13  5:05 ` [PATCH v5 1/4] Gold: Add targ_extra_little_endian to configure.ac YunQiang Su
2023-11-13  5:05 ` [PATCH v5 2/4] Gold/MIPS: Drop mips*le/mips*el* triple pattern YunQiang Su
2023-11-13  5:05 ` [PATCH v5 3/4] Gold/MIPS: Add targ_extra_size=64 for mips32 triples YunQiang Su
2023-11-17 14:35   ` Nick Clifton
2023-11-17 14:57     ` YunQiang Su
2023-11-20 12:11       ` Nick Clifton
2023-11-13  5:05 ` [PATCH v5 4/4] Gold/MIPS: Add mips64*/mips64*el triple support YunQiang Su
2023-11-13  5:11 ` YunQiang Su [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=CAKcpw6X3vZ1Of9nNvQDKtCRYpzva8kSf7T-1T-nkOuU3TVA5Tw@mail.gmail.com \
    --to=wzssyqa@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=doko@debian.org \
    --cc=nickc@redhat.com \
    --cc=yunqiang.su@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).