public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Georg-Johann Lay <avr@gjlay.de>
To: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: [avr, patch 0/1] Addendum to PR31124: Don't PROVIDE __flmap_init_label
Date: Wed, 31 Jan 2024 09:43:07 +0100	[thread overview]
Message-ID: <b48c0734-cdfb-4ba2-ab90-c4a6b6789d0a@gjlay.de> (raw)
In-Reply-To: <c19628e3-f5be-4029-852a-4f6d991a5890@redhat.com>



Am 30.01.24 um 14:44 schrieb Nick Clifton:
> Hi Johann,
> 
>> this patch removes PROVIDE from __flmap_init_label,
> 
> Err, I think that you forgot to attach the patch ...


Hi Nick,

the patch is in a separate e-mail that only contains the commit
message and the patch:

https://sourceware.org/pipermail/binutils/2024-January/132247.html

Thanks,

Johann

>> which is needed to make the startup code from AVR-LibC work
>> with versions of Binutils that don't have PR31124: The start
>> code would weakly define __flmap_init_label, but when Binutils DOES
>> support PR31124, then we need the correct values, hence no PROVIDE.
>>
>> If approved, please apply.
>>
>> Also if it is possible to squeeze this in v2.42, that would be great.
> 
> Assuming that it is OK for the mainline, then I will also apply it to 
> the 2.42 branch.
> But - since the 2.42 release is now out, it will only affect people who 
> check out the
> branch, or if we make a 2.42.1 point release...
> 
> Cheers
>     Nick


  reply	other threads:[~2024-01-31  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 13:37 [avr, patch 0/1] Addendum to PR3124: " Georg-Johann Lay
2024-01-30 13:44 ` Nick Clifton
2024-01-31  8:43   ` Georg-Johann Lay [this message]
2024-01-31 11:25     ` [avr, patch 0/1] Addendum to PR31124: " Nick Clifton
2024-01-30 13:53 ` [avr, patch 1/1] " Georg-Johann Lay

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=b48c0734-cdfb-4ba2-ab90-c4a6b6789d0a@gjlay.de \
    --to=avr@gjlay.de \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.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).