Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org,
	Raphael Pavlidis <raphael.pavlidis@gmail.com>,
	Adrian Perez de Castro <aperez@igalia.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/cage: properly propagate wlroots dependencies
Date: Wed, 17 Dec 2025 21:04:03 +0100	[thread overview]
Message-ID: <e3344bb3e6906c838077115c384edfd0@free.fr> (raw)
In-Reply-To: <20251215225837.1257574-1-thomas.petazzoni@bootlin.com>

On 15/12/2025 23:58, Thomas Petazzoni via buildroot wrote:
> Commit 00fb3a57cbaedb8df43f75f0e891423c1ef7d8c6 added a wlroots ->
> libgbm dependency, but forgot to propagate it to package/cage.
> 
> Fixes:
> 
>   
> https://autobuild.buildroot.net/results/dc185c3d4886e9cfd9e6f46b50b864e5b2f28605/
> 
> Cc: Raphael Pavlidis <raphael.pavlidis@gmail.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2025-12-17 20:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 22:58 [Buildroot] [PATCH 1/2] package/cage: properly propagate wlroots dependencies Thomas Petazzoni via buildroot
2025-12-15 22:58 ` [Buildroot] [PATCH 2/2] package/sway: " Thomas Petazzoni via buildroot
2025-12-15 23:46   ` Adrian Perez de Castro
2025-12-17 17:13   ` Raphael Pavlidis
2026-01-07 17:48   ` Arnout Vandecappelle via buildroot
2025-12-15 23:45 ` [Buildroot] [PATCH 1/2] package/cage: " Adrian Perez de Castro
2025-12-17 20:04 ` Julien Olivain via buildroot [this message]
2026-01-07 17:48 ` Arnout Vandecappelle via buildroot

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=e3344bb3e6906c838077115c384edfd0@free.fr \
    --to=buildroot@buildroot.org \
    --cc=aperez@igalia.com \
    --cc=ju.o@free.fr \
    --cc=raphael.pavlidis@gmail.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