From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Niklas Cassel via buildroot <buildroot@buildroot.org>
Cc: Greg Ungerer <gregungerer@westnet.com.au>,
Niklas Cassel <niklas.cassel@wdc.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Waldemar Brodkorb <mail@waldemar-brodkorb.de>,
Jesse T <mr.bossman075@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/elf2flt: update to version 2023.09
Date: Thu, 14 Sep 2023 22:33:39 +0200 [thread overview]
Message-ID: <20230914223339.5ee8e854@windsurf> (raw)
In-Reply-To: <20230912110420.1111238-1-niklas.cassel@wdc.com>
On Tue, 12 Sep 2023 13:04:20 +0200
Niklas Cassel via buildroot <buildroot@buildroot.org> wrote:
> Several of our patches have been accepted upstream and are included in
> elf2flt version 2023.09.
>
> Patch 0001-elf2flt-handle-binutils-2.34.patch is upstream as of commit
> c70b9f208979 ("elf2flt: handle binutils >= 2.34").
>
> Patch 0002-elf2flt.ld-reinstate-32-byte-alignment-for-.data-sec.patch is
> upstream as of commit 679c94adf27c ("elf2flt.ld: reinstate 32 byte
> alignment for .data section").
>
> Patch 0003-elf2flt-add-riscv-64-bits-support.patch is upstream as of
> commit c5c8043c4d79 ("elf2flt: add riscv 64-bits support").
>
> Patch 0008-riscv64-add-more-relocations-required-to-be-handled.patch was
> squashed into upstream commit c5c8043c4d79 ("elf2flt: add riscv 64-bits
> support") during upstreaming.
>
> Patch 0006-xtensa-fix-text-relocations.patch is upstream as of commit
> 26dfb54a59c8 ("elf2flt: xtensa: fix text relocations").
>
> Patch 0007-elf2flt-remove-use-of-BFD_VMA_FMT.patch is upstream as of
> commit a36df7407d9e ("elf2flt: remove use of BFD_VMA_FMT").
>
> Patch 0004-elf2flt-create-a-common-helper-function.patch simply added
> a helper function to make the changes in the follow-up patch
> 0005-elf2flt-fix-fatal-error-regression-on-m68k-xtensa-ri.patch
> less intrusive.
>
> Patch 0005-elf2flt-fix-fatal-error-regression-on-m68k-xtensa-ri.patch
> is no longer needed as upstream has reverted the commit that necessitated
> this patch, see upstream commit 35c692ca4546 ("Revert "elf2flt: fix for
> segfault on some ARM ELFs""). The problem that the reverted upstream patch
> solved is now instead solved by the combination of upstream commits
> 7a59b265c2dc ("Revert "elf2flt: fix relocations for read-only data"") and
> a934fb42cf59 ("elf2flt: force ARM.exidx section into text").
>
> Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
> ---
> Resending from an email address that is subscribed to the buildroot
> mailing list, since my previous mail got rejected.
Amazing to see that we're down to 0 patches against elf2flt. Thanks for
doing this, and thanks for the testing. Just the update of the
.checkpackageignore file was missing, so I did that when applying.
Thanks again!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-14 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 11:04 [Buildroot] [PATCH] package/elf2flt: update to version 2023.09 Niklas Cassel via buildroot
2023-09-13 8:15 ` Waldemar Brodkorb
2023-09-14 20:33 ` Thomas Petazzoni via buildroot [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=20230914223339.5ee8e854@windsurf \
--to=buildroot@buildroot.org \
--cc=Damien.LeMoal@wdc.com \
--cc=gregungerer@westnet.com.au \
--cc=mail@waldemar-brodkorb.de \
--cc=mr.bossman075@gmail.com \
--cc=niklas.cassel@wdc.com \
--cc=thomas.petazzoni@bootlin.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