From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix problem with undefined umode_t type in 3.3 kernel headers
Date: Thu, 29 Mar 2012 10:47:14 +0200 [thread overview]
Message-ID: <87wr63g5f1.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1332580484-4489-1-git-send-email-spdawson@gmail.com> (spdawson@gmail.com's message of "Sat, 24 Mar 2012 09:14:44 +0000")
>>>>> "spdawson" == spdawson <spdawson@gmail.com> writes:
spdawson> From: Simon Dawson <spdawson@gmail.com>
spdawson> The 3.3 kernel headers define the umode_t type within a
spdawson> __KERNEL__ preprocessor ifdef region. This results in a
spdawson> broken kernel header in the buildroot toolchain.
Committed, thanks. It seems socat/syslinux should get updated to not
include this header, but as there's no upstream releases fixing this it
makes sense to add it for now.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-03-29 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 9:14 [Buildroot] [PATCH] Fix problem with undefined umode_t type in 3.3 kernel headers spdawson at gmail.com
2012-03-29 8:47 ` Peter Korsgaard [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=87wr63g5f1.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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