From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
buildroot@buildroot.org,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Petr Vorel <pevik@seznam.cz>
Subject: Re: [Buildroot] [PATCH 1/2] package/ltp-testsuite: bump version to 20230127
Date: Sun, 16 Apr 2023 09:45:27 +0200 [thread overview]
Message-ID: <20230416074527.GV2819@scaer> (raw)
In-Reply-To: <CAB1t1CwZS7vreP7z4k5g3Np8JLO-_HEEQczin45pS9RtMS1H+A@mail.gmail.com>
Petr, All,
On 2023-04-16 01:21 +0200, Petr Vorel spake thusly:
> On Sat, 15 Apr 2023 at 10:41, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2023-04-15 10:05 +0200, Yann E. MORIN spake thusly:
[--SNIP--]
> > Now, we could also very well decide that ltp-testsuite depends on kernel
> > headers >= 5.11 for musl toolchains, which would probably be the actual
> > solution, if upstream really does not want to fix that situation.
> Thanks for a suggestion, I'd really try to add the dependency for musl:
> depends on !BR2_TOOLCHAIN_USES_MUSL || BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_11
> I'll put the change in a separate commit, with removal of the patch
> and explaining
> the reason (leaving the actual upgrade in a separate commit), so that
> it's easier
> for people to find the reason. If people complain, we can ask upstream
> to reconsider
> or reintroduce the patch. But I'd like to avoid extra work in case
> nobody bothers.
That sounds like a good plan, indeed.
Also, as I understand it, patch 2, which fixes mount_attr detection,
should come first, because it already applies to the current version,
no? If not, then it should be squashed into the version bump.
So, probably, the series should go like:
package/ltp-testsuite: backport mount_attr fix on older glibc
package/ltp-testsuite: disable for musl with kernel headers < 5.11
package/ltp-testsuite: bump to 20230127
Thanks!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-04-16 7:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 20:14 [Buildroot] [PATCH 1/2] package/ltp-testsuite: bump version to 20230127 Petr Vorel
2023-04-05 20:14 ` [Buildroot] [PATCH 2/2] package/ltp-testsuite: Backport fix for buildroot toolchain Petr Vorel
2023-04-05 20:27 ` [Buildroot] [PATCH 1/2] package/ltp-testsuite: bump version to 20230127 Petr Vorel
2023-04-10 17:24 ` Yann E. MORIN
2023-04-12 18:12 ` Petr Vorel
2023-04-14 19:01 ` Yann E. MORIN
2023-04-14 20:54 ` Petr Vorel
2023-04-15 8:05 ` Yann E. MORIN
2023-04-15 8:40 ` Yann E. MORIN
2023-04-15 23:21 ` Petr Vorel
2023-04-16 7:45 ` Yann E. MORIN [this message]
2023-04-16 15:08 ` Petr Vorel
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=20230416074527.GV2819@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=petr.vorel@gmail.com \
--cc=pevik@seznam.cz \
--cc=thomas.petazzoni@free-electrons.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