All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Thomas Devoogdt <thomas.devoogdt@barco.com>,
	Jesse Van Gavere <jesseevg@gmail.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/3 next] package/qt6/qt6serialport: use the CMAKE_NINJA flag
Date: Mon, 7 Aug 2023 23:26:46 +0200	[thread overview]
Message-ID: <20230807232646.76210d7e@windsurf> (raw)
In-Reply-To: <20230807145839.2375839-1-thomas.devoogdt@barco.com>

On Mon,  7 Aug 2023 16:58:37 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:

> Use the newly introduce backend option (4cf79d9b71ff5cf2aede3f21e09ade7c7ac59606)
> to specify what cmake backend to use, instead of special-coding it's use.
> 
> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
> ---
>  package/qt6/qt6serialport/qt6serialport.mk | 16 ++--------------
>  1 file changed, 2 insertions(+), 14 deletions(-)

All three applied to next, 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

  parent reply	other threads:[~2023-08-07 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 14:58 [Buildroot] [PATCH v1 1/3 next] package/qt6/qt6serialport: use the CMAKE_NINJA flag Thomas Devoogdt
2023-08-07 14:58 ` [Buildroot] [PATCH v1 2/3 next] package/qt6/qt6serialbus: " Thomas Devoogdt
2023-08-07 14:58 ` [Buildroot] [PATCH v1 3/3 next] package/qt6/qt6base: " Thomas Devoogdt
2023-08-07 21:26 ` Thomas Petazzoni via buildroot [this message]
2023-08-07 21:31 ` [Buildroot] [PATCH v1 1/3 next] package/qt6/qt6serialport: " Yann E. MORIN
2023-08-08  5:24   ` Thomas Devoogdt

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=20230807232646.76210d7e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=jesseevg@gmail.com \
    --cc=thomas.devoogdt@barco.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas@devoogdt.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 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.