From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <adam.duskett@amarulasolutions.com>,
Paul Cercueil <paul@crapouillou.net>
Cc: Adrian Perez de Castro <aperez@igalia.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/wlroots: Update patch with upstream status
Date: Mon, 5 Feb 2024 22:29:49 +0100 [thread overview]
Message-ID: <20240205222949.2805f50f@windsurf> (raw)
In-Reply-To: <20240121204252.152952-2-adam.duskett@amarulasolutions.com>
Hello Adam,
+Paul Cercueil in Cc, see below.
On Sun, 21 Jan 2024 13:42:52 -0700
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:
> package/wlroots/0001-Add-feature-macros-to-more-C-files-.patch has been
> rejected upstream, and the initial pull request was moved to the
> freedesktop gitlab. Update the patch to reflect these changes.
>
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Thanks, applied!
Paul: could you follow-up with upstream (either wlroots, or uclibc, or
both) to try to find an acceptable solution so that some day we can
drop this patch?
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-05 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 20:42 [Buildroot] [PATCH 1/2] package/wlroot: vulkan renderer depends on vulkan loader Adam Duskett
2024-01-21 20:42 ` [Buildroot] [PATCH 2/2] package/wlroots: Update patch with upstream status Adam Duskett
2024-02-05 21:29 ` Thomas Petazzoni via buildroot [this message]
2024-02-06 9:52 ` Paul Cercueil
2024-02-12 18:13 ` Paul Cercueil
2024-02-29 15:40 ` Peter Korsgaard
2024-02-05 21:28 ` [Buildroot] [PATCH 1/2] package/wlroot: vulkan renderer depends on vulkan loader Thomas Petazzoni via buildroot
2024-02-29 15:40 ` 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=20240205222949.2805f50f@windsurf \
--to=buildroot@buildroot.org \
--cc=adam.duskett@amarulasolutions.com \
--cc=aperez@igalia.com \
--cc=paul@crapouillou.net \
--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