From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] directfb: depends on NPTL threading
Date: Sun, 17 Jul 2016 15:08:02 +0200 [thread overview]
Message-ID: <20160717150802.359bc380@free-electrons.com> (raw)
In-Reply-To: <20160708222129.GA22796@waldemar-brodkorb.de>
Hello,
On Sat, 9 Jul 2016 00:21:29 +0200, Waldemar Brodkorb wrote:
> Fixes following autobuild failure:
> http://autobuild.buildroot.net/results/162db0d62075a16c7abae1229676e2cdb29fe953/
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> v1 -> v2:
> - rather adding an experimental patch without runtime testing for
> an unmaintained software, we depend on NPTL as discussed with
> Thomas Petazzoni on IRC
> ---
> package/directfb/Config.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I've applied, after adjusting the Config.in comment, as noticed by
Romain Naour.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-07-17 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 22:21 [Buildroot] [PATCH v2] directfb: depends on NPTL threading Waldemar Brodkorb
2016-07-16 15:36 ` Romain Naour
2016-07-17 13:08 ` Thomas Petazzoni [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=20160717150802.359bc380@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