From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] libcap: add patch to fix build issue with old kernel headers
Date: Thu, 17 Mar 2016 09:20:14 +0100 [thread overview]
Message-ID: <20160317092014.20ca2072@free-electrons.com> (raw)
In-Reply-To: <87pouu6o1o.fsf@dell.be.48ers.dk>
Hello,
On Wed, 16 Mar 2016 23:44:19 +0100, Peter Korsgaard wrote:
> > My commit log is talking about XATTR_SECURITY_PREFIX, not
> > XATTR_CAPS_SUFFIX.
>
> Well, you wrote ".. but using XATTR_SECURITY_PREFIX and
> XATTR_CAPS_SUFFIX which were defined in the kernel-only part of
> <linux/xattr.h>"
Gaah, bad commit log :-/ Sorry about that.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-17 8:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 20:20 [Buildroot] [PATCH 1/4] libcap: bump version Thomas Petazzoni
2016-03-16 20:20 ` [Buildroot] [PATCH 2/4] libcap: add patch to fix build issue with old kernel headers Thomas Petazzoni
2016-03-16 22:16 ` Peter Korsgaard
2016-03-16 22:34 ` Thomas Petazzoni
2016-03-16 22:44 ` Peter Korsgaard
2016-03-17 8:20 ` Thomas Petazzoni [this message]
2016-03-16 20:20 ` [Buildroot] [PATCH 3/4] libcap, cdrkit, dvdrw-tools, fastd, squid: remove headers >= 3.0 dependency Thomas Petazzoni
2016-03-16 22:23 ` Peter Korsgaard
2016-03-16 20:20 ` [Buildroot] [PATCH 4/4] lxc: remove dependency on headers >= 3.0 Thomas Petazzoni
2016-03-16 22:31 ` Peter Korsgaard
2016-03-16 22:36 ` Thomas Petazzoni
2016-03-16 22:45 ` Peter Korsgaard
2016-03-16 22:49 ` Arnout Vandecappelle
2016-03-17 6:22 ` Peter Korsgaard
2016-03-16 22:09 ` [Buildroot] [PATCH 1/4] libcap: bump version Peter Korsgaard
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=20160317092014.20ca2072@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