From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/libva: bump version to 2.2.0
Date: Sun, 29 Jul 2018 00:23:56 +0200 [thread overview]
Message-ID: <s07v2fxkc3.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20180714221102.3f88c992@windsurf
Am Sat, 14 Jul 2018 22:11:02 +0200 schrieb Thomas Petazzoni:
> Please fix this properly, by adding an autoconf check testing if
> -fstack-protector is available and/or making sure CFLAGS passed in the
> environment are properly taken into account.
Hi Thomas,
done (hopefully): https://github.com/intel/libva/pull/226
Now I will wait for their review and continue with the remaining va
packages afterwards.
Regards, Bernd
prev parent reply other threads:[~2018-07-28 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 10:55 [Buildroot] [PATCH 1/3] package/libva: bump version to 2.2.0 Bernd Kuhls
2018-07-14 10:55 ` [Buildroot] [PATCH 2/3] package/libva-intel-driver: " Bernd Kuhls
2018-07-14 10:55 ` [Buildroot] [PATCH 3/3] package/libva-utils: " Bernd Kuhls
2018-07-14 20:11 ` [Buildroot] [PATCH 1/3] package/libva: " Thomas Petazzoni
2018-07-28 22:23 ` Bernd Kuhls [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=s07v2fxkc3.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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