From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt5base: remove unused definition
Date: Sat, 30 Jun 2018 18:10:17 +0200 [thread overview]
Message-ID: <20180630181017.07d8e860@windsurf.home> (raw)
In-Reply-To: <20180630125713.4302-1-gael.portay@savoirfairelinux.com>
Hello,
On Sat, 30 Jun 2018 08:57:13 -0400, Ga?l PORTAY wrote:
> Since commit 81fb33af2a (qt5base: correct eglfs support in
> qmake.conf.in) the definition QT5BASE_CONFIGURE_QMAKE_CONFIG is left
> unused.
>
> Remove it since it is not used anymore.
>
> Signed-off-by: Ga?l PORTAY <gael.portay@savoirfairelinux.com>
> ---
> package/qt5/qt5base/qt5base.mk | 1 -
> 1 file changed, 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-30 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 12:57 [Buildroot] [PATCH] qt5base: remove unused definition Gaël PORTAY
2018-06-30 16:02 ` Yann E. MORIN
2018-06-30 16:10 ` Thomas Petazzoni [this message]
2018-07-19 9:56 ` 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=20180630181017.07d8e860@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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