Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Vincent Fazio <vfazio@xes-inc.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/mesa3d-headers: fix install of dri.pc
Date: Tue, 26 Jul 2022 18:46:01 +0200	[thread overview]
Message-ID: <20220726184601.09b011ee@windsurf> (raw)
In-Reply-To: <20220726151536.2937333-1-vfazio@xes-inc.com>

On Tue, 26 Jul 2022 10:15:36 -0500
Vincent Fazio <vfazio@xes-inc.com> wrote:

> With the version bump to 22.x, the dri.pc file was no longer deployed as
> it was believed to not be provided.
> 
> While it was temporarily missing from upstream as part of deprecating
> the classic driver, it was reintroduced prior to the 22.0 release via:
>   https://gitlab.freedesktop.org/mesa/mesa/-/commit/3ae3569d822c2546c4c748090f8a6c8016f763ea
> 
> This file is still necessary to build Xorg server. See previous commits:
>   9014c21cac
>   7468b60e7c
> 
> Fixes: 6c25d1099 ("package/{mesa3d, mesa3d-headers}: bump version to 22.1.3")
> 
> Signed-off-by: Vincent Fazio <vfazio@xes-inc.com>
> ---
>  package/mesa3d-headers/mesa3d-headers.mk | 10 ++++++++++
>  1 file changed, 10 insertions(+)

For some reason, the lines you re-added had bogus indentation (spaces
instead of tabs), which was reported by check-package. I fixed that up
and applied. Thanks!

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

      reply	other threads:[~2022-07-26 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 15:15 [Buildroot] [PATCH] package/mesa3d-headers: fix install of dri.pc Vincent Fazio
2022-07-26 16:46 ` 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=20220726184601.09b011ee@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd.kuhls@t-online.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vfazio@xes-inc.com \
    --cc=yann.morin.1998@free.fr \
    /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