From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt53d, qt5serialbus: move to technology preview section
Date: Tue, 11 Oct 2016 11:26:40 +0200 [thread overview]
Message-ID: <20161011112640.3005e46c@free-electrons.com> (raw)
In-Reply-To: <20161011024600.4939-1-kraai@ftbfs.org>
Hello,
On Mon, 10 Oct 2016 19:46:00 -0700, Matt Kraai wrote:
> Signed-off-by: Matt Kraai <kraai@ftbfs.org>
qt5serialbus is indeed a "technology preview" in Qt 5.6, but I believe
qt3d was a technology preview in Qt 5.5, but then promoted as an
integral part of Qt as of Qt 5.6.
Do you have a source of information to confirm what your patch is doing?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-11 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 2:46 [Buildroot] [PATCH] qt53d, qt5serialbus: move to technology preview section Matt Kraai
2016-10-11 9:26 ` Thomas Petazzoni [this message]
2016-10-11 11:35 ` Matt Kraai
2016-10-15 12:24 ` Thomas Petazzoni
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=20161011112640.3005e46c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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