From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] linux-libc-headers (2.6.24): Add falloc.h to kernel exported headers
Date: Thu, 30 Sep 2010 10:54:37 +0200 [thread overview]
Message-ID: <4CA4504D.6080900@dresearch.de> (raw)
In-Reply-To: <1285774983-31373-1-git-send-email-t.fromm@dresearch.de>
Am 29.09.2010 17:43, schrieb Thilo Fromm:
> upstream: OE-only
> This adds include/linux/falloc.h to the list of files exported by the kernel
> to the C library. The include file is required for building e.g. a recent
> util-linux-ng against 2.6.24.
>
> Starting from 2.6.25 a similar patch has been accepted upstream (the mainline
> kernel). For 2.6.24, however, falloc.h is not exported although it's present.
>
> Signed-off-by: Thilo Fromm <t.fromm@dresearch.de>
Acked-by: Steffen Sledz <sledz@dresearch.de>
--
Steffen Sledz
DResearch Digital Media Systems GmbH
Otto-Schmirgal-Str.3, D-10319 Berlin, Germany
Tel: +49 (30) 515932237 mailto:sledz@DResearch.DE
Fax: +49 (30) 515932299 http://www.DResearch.DE
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 54412;
Ust.-IDNr. DE169013825; WEEE Reg.-Nr. DE 85995642
next prev parent reply other threads:[~2010-09-30 8:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 15:15 falloc.h missing: util-linux-ng-2.17 build fails against 2.6.24 Thilo Fromm
2010-09-27 15:23 ` [PATCH] Add falloc.h to the exported kernel header files Thilo Fromm
2010-09-29 9:27 ` Steffen Sledz
2010-09-29 13:08 ` Paul Menzel
2010-09-29 15:31 ` Thilo Fromm
2010-09-29 22:06 ` Paul Menzel
2010-09-29 15:43 ` [PATCH v2] linux-libc-headers (2.6.24): Add falloc.h to kernel exported headers Thilo Fromm
2010-09-30 8:54 ` Steffen Sledz [this message]
2010-09-30 9:16 ` Paul Menzel
2010-09-30 10:50 ` Thilo Fromm
2010-09-30 12:40 ` [PATCH v3] linux-libc-headers_2.6.24: " Thilo Fromm
2010-09-30 13:14 ` Paul Menzel
2010-09-30 14:09 ` Thilo Fromm
2010-09-30 14:36 ` Paul Menzel
2010-10-01 7:07 ` [PATCH v4] " Thilo Fromm
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=4CA4504D.6080900@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@lists.openembedded.org \
/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.