From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libseccomp: needs headers >= 3.12
Date: Tue, 31 Mar 2015 23:46:26 +0200 [thread overview]
Message-ID: <20150331234626.045d04b4@free-electrons.com> (raw)
In-Reply-To: <1427819637-2471-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Tue, 31 Mar 2015 18:33:57 +0200, Bernd Kuhls wrote:
> +comment "libseccomp needs headers >= 3.12"
This should have been "libseccomp needs a tpolchain w/ headers >= 3.12"
I've committed your patch. Baruch, if you really want to have
libseccomp on kernel olders than 3.12, do not hesitate to send a
followup patch. Since the issue was affecting the autobuilders, I
wanted to get rid of it as soon as possible.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-03-31 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 16:33 [Buildroot] [PATCH 1/1] package/libseccomp: needs headers >= 3.12 Bernd Kuhls
2015-03-31 16:57 ` Baruch Siach
2015-03-31 16:59 ` Bernd Kuhls
2015-03-31 17:11 ` Baruch Siach
2015-03-31 21:33 ` Thomas Petazzoni
2015-03-31 21:46 ` 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=20150331234626.045d04b4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.