From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] neard: fix build with kernel headers 3.1 - 3.6
Date: Mon, 25 Feb 2013 11:40:38 +0100 [thread overview]
Message-ID: <20130225114038.4b045521@skate> (raw)
In-Reply-To: <5121D7D2.1000401@mind.be>
Dear Arnout Vandecappelle,
On Mon, 18 Feb 2013 08:27:14 +0100, Arnout Vandecappelle wrote:
> > Committed, thanks. Don't forget to send upstream.
>
> Thomas, did you ever send the original patch upstream?
No, I did not. Since the patch carries an entire copy of the kernel
header, I am fairly sure that upstream will not be very interested.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-25 10:40 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
2013-02-25 10:40 ` Thomas Petazzoni [this message]
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=20130225114038.4b045521@skate \
--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