From: Peter Korsgaard <peter@korsgaard.com>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: Samuel Martin <s.martin49@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/4] package/wpewebkit: security bump to version 2.44.2
Date: Sun, 23 Jun 2024 11:03:38 +0200 [thread overview]
Message-ID: <877cegowt1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240619140513.GB831334@igalia.com> (Adrian Perez de Castro's message of "Wed, 19 Jun 2024 14:05:13 +0300")
>>>>> "Adrian" == Adrian Perez de Castro <aperez@igalia.com> writes:
Hi,
>> > Committed to 2024.02.x, thanks.
>>
>> this bump broke the build on ARM NEON (again). Since the gitlab issue tracker doesn't seem to notify the ML
>> here is the link: https://gitlab.com/buildroot.org/buildroot/-/issues/3
> There was a fix that landed in the WebKit "main" branch some days
> ago and I did a backport to the 2.44 branch; I have already started
> preparing a patch for Buildroot.
Thanks. What happened to that patch?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-06-23 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 10:34 [Buildroot] [PATCH 2/4] package/wpewebkit: security bump to version 2.44.2 Michael Nosthoff via buildroot
2024-06-19 11:05 ` Adrian Perez de Castro
2024-06-23 9:03 ` Peter Korsgaard [this message]
2024-06-24 20:04 ` Adrian Perez de Castro
2024-06-25 10:27 ` Michael Nosthoff via buildroot
-- strict thread matches above, loose matches on Subject: below --
2024-05-22 9:16 [Buildroot] [PATCH 0/4] Update WPE WebKit to the 2.44 release series Adrian Perez de Castro
2024-05-22 9:16 ` [Buildroot] [PATCH 2/4] package/wpewebkit: security bump to version 2.44.2 Adrian Perez de Castro
2024-05-29 6:16 ` Peter Korsgaard
2024-05-29 14:31 ` Adrian Perez de Castro
2024-06-08 16:47 ` Peter Korsgaard
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=877cegowt1.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=aperez@igalia.com \
--cc=buildroot@buildroot.org \
--cc=s.martin49@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.