Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-08
Date: Sun, 26 May 2019 20:36:08 +0200	[thread overview]
Message-ID: <20190526203608.15723248@windsurf> (raw)
In-Reply-To: <1558874852.local-6573d1a7-8bd6-v1.5.5-b7939d38@getmailspring.com>

Hello,

On Sun, 26 May 2019 16:08:47 +0200
LP C <lpdev@cordier.org> wrote:

> https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/recipes-multimedia/libva/intel-media-driver/0001-linux-fix-build-when-using-musl.patch
> seems to fix the issue with musl. This patch does not break the build with standard libc. As it is a patch from yocto, can I use it directly or is there any license restriction to do so?

You can use it directly, just add your own Signed-off-by below the one
of the patch author.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-05-26 18:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-08 Thomas Petazzoni
2019-05-09 21:03 ` Thomas Petazzoni
2019-05-09 21:19   ` Giulio Benetti
2019-05-11 21:00     ` Giulio Benetti
2019-05-14 20:36       ` Yann E. MORIN
2019-05-14 21:47         ` Giulio Benetti
2019-05-09 21:41   ` LP C
2019-05-10  8:59   ` Vadym Kochan
2019-05-13 11:20   ` Julien Boibessot
2019-05-13 11:31     ` Thomas Petazzoni
2019-05-13 15:59       ` Julien Boibessot
2019-05-25 15:31         ` Arnout Vandecappelle
2019-05-26 14:08           ` LP C
2019-05-26 18:36             ` Thomas Petazzoni [this message]
2019-05-23  7:07   ` Nylon Chen

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=20190526203608.15723248@windsurf \
    --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