public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: Sam James <sam@gentoo.org>, binutils@sourceware.org
Subject: Re: [PATCH 1/2] ld: Fix relocatable.d XFAIL/notarget entry for hppa
Date: Thu, 10 Aug 2023 03:55:33 +0100	[thread overview]
Message-ID: <877cq37gi8.fsf@gentoo.org> (raw)
In-Reply-To: <d5d872fb-c3e1-5c11-2ce5-a099929ddd24@suse.com>


Jan Beulich <jbeulich@suse.com> writes:

> On 08.08.2023 19:53, Sam James wrote:
>> 
>> Jan Beulich <jbeulich@suse.com> writes:
>> 
>>> On 08.08.2023 03:23, Sam James via Binutils wrote:
>>>> PR 30734
>>>> * ld/testsuite/ld-elf/relocatable.d: Fix notarget entry for hppa to match
>>>>   hppa{1.1,2.0}*, like hppa2.0-unknown-linux-gnu which Gentoo uses.
>>>>
>>>> Signed-off-by: Sam James <sam@gentoo.org>
>>>
>>> Since the two patches deal with the only two outliers, I'd consider these
>>> to be at least very close to obvious. Feel free to put in. Yet in the
>>> future for arch-specific changes please remember to Cc respective arch
>>> maintainers.
>> 
>> 1. ACK, pushed. Thank you. Sorry, I was a bit too conservative here.
>> 2. Fair point, I will do this in future.
>> 
>> What's the rule for backports? Can I just do those if obvious?
>
> Unless while the tree is closed, I'd say generally yes, but after waiting
> a little (to see whether there's fallout nevertheless, as appears to be
> the case here). Of course it also doesn't hurt asking.
>
>> What
>> about if they're not my commits but I've tested them and they're
>> straightforward?
>
> I'm less sure here - I, for one, would ask in such a case, despite (now)
> being global maintainer.

Thank you for the advice Jan!



  reply	other threads:[~2023-08-10  2:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  1:23 Sam James
2023-08-08  1:24 ` [PATCH 2/2] ld: Fix retain7a.d " Sam James
2023-08-08  6:44 ` [PATCH 1/2] ld: Fix relocatable.d " Jan Beulich
2023-08-08 17:53   ` Sam James
2023-08-09  6:20     ` Jan Beulich
2023-08-10  2:55       ` Sam James [this message]
2023-08-09  4:40 ` Alan Modra
2023-08-10  2:54   ` Sam James

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=877cq37gi8.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.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).