From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] neard: fix build with kernel headers 3.1 - 3.6
Date: Mon, 18 Feb 2013 08:27:14 +0100 [thread overview]
Message-ID: <5121D7D2.1000401@mind.be> (raw)
In-Reply-To: <87621qmvzc.fsf@dell.be.48ers.dk>
On 17/02/13 23:11, Peter Korsgaard wrote:
>>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
>
> Arnout> From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
> Arnout> neard uses the linux/nfc.h header which is fairly recent, so we have a
> Arnout> patch that creates linux-nfc.h and uses it if necessary. However, since
> Arnout> the bump to 0.9, neard uses some symbols that are introduced in linux 3.7
> Arnout> so the build fails with headers 3.1 (which introduced nfc.h) to 3.6.
>
> Arnout> To resolve that, add a check for one of the newly introduced symbols
> Arnout> (that is used by neard).
>
> Arnout> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Arnout> ---
> Arnout> v2: Forgot to include <sys/socket.h>.
>
> Arnout> Probably wanted for 2013.02.
>
> Committed, thanks. Don't forget to send upstream.
Thomas, did you ever send the original patch upstream?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-02-18 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 17:02 [Buildroot] [PATCH] neard: fix build with kernel headers 3.1 - 3.6 Arnout Vandecappelle
2013-02-16 17:34 ` Arnout Vandecappelle
2013-02-17 22:11 ` Peter Korsgaard
2013-02-18 7:27 ` Arnout Vandecappelle [this message]
2013-02-25 10:40 ` Thomas Petazzoni
2013-02-25 20:41 ` Arnout Vandecappelle
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=5121D7D2.1000401@mind.be \
--to=arnout@mind.be \
--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