From: Thilo Fromm <t.fromm@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v3] linux-libc-headers_2.6.24: Add falloc.h to kernel exported headers
Date: Thu, 30 Sep 2010 16:09:09 +0200 [thread overview]
Message-ID: <4CA49A05.9030500@dresearch.de> (raw)
In-Reply-To: <1285852480.3805.79.camel@mattotaupa>
Hello Paul,
>> 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.
>>
[...]
>> .../linux-libc-headers/files/export_falloc_h.patch | 11 +++++++++++
>> +++ b/recipes/linux-libc-headers/files/export_falloc_h.patch
>> @@ -0,0 +1,11 @@
>> +upstream: OE-only
>
> Hmm, do you think it is OE only. As written in my other message I
> consider this an upstream patch, which has been committed already.
>
> upstream: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=040922c04cf2c8ac70be2e88a8a9614ecdb41d2e
> comment: Patch is present in Linux kernel>= 2.6.25.
Technically, this upstreamed patch is not my patch. Upstream is way
older, it's from a different author, etc. Plus it's included in
successive kernel releases, but it's not in the version affected by my
patch. From my point of view my patch is an OE-only hack because it
back-ports to an older kernel version a different patch which originated
from OE (?) a long time ago and then went mainline.
I'll of course change this to your suggestion if this is a problem. I
did not do this yet so my patch won't get confused with the original one
that went mainline.
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Developer
DResearch Digital Media Systems GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:t.fromm@dresearch.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB:54412
Ust.-IDNr. DE169013825; WEEE Reg.-Nr. DE 85995642
Geschäftsführer: Dr. M. Weber, W. Mögle
next prev parent reply other threads:[~2010-09-30 14:09 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
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 [this message]
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=4CA49A05.9030500@dresearch.de \
--to=t.fromm@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.