From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/network-manager: add patches to build with kernel headers 3.2
Date: Thu, 25 Jun 2015 00:56:48 +0200 [thread overview]
Message-ID: <20150624225647.GR28656@t61> (raw)
In-Reply-To: <55891190.7080800@mind.be>
Hi there,
> On 06/22/15 12:43, Petr Vorel wrote:
> > From: Petr Vorel <petr.vorel@gmail.com>
> "works" as in run-time tested?
I've done some brief tests, I'll do more testing probably this week. Ok, I should have
wait and post the patch after more testing. Anyway I need to get it work even on lower
kernel than 3.2 (obviously some features will be missing, but NetworkManager cannot
crash). Upstream is willing to accept simple patches which fixes behaviour on older
kernels.
> Upstream status?
Not sure if I understand your question. The patch was taken from upstream.
> > - depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_7
> > + depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_2
> Basically it _may_ also work with lower kernel headers but hasn't been tested,
> right? Ideally, it would be nice to do a (build-)test with 2.6.34-ish.
Why 2.6.34-ish? The minimum kernel version in toolchain/toolchain-common.in after
BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_0 is 2.6, which is unspecified.
> Or else, you could add a comment saying that it could work with lower headers. The
> minimal headers version was anyway only introduced to fix an autobuild failure.
Do you mean to keep BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_7 and mention in "help" lower
versions?
> Regards,
> Arnout
Kind regards,
Petr
next prev parent reply other threads:[~2015-06-24 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 10:43 [Buildroot] [PATCH v3 1/1] package/network-manager: add patches to build with kernel headers 3.2 Petr Vorel
2015-06-23 7:58 ` Arnout Vandecappelle
2015-06-24 22:56 ` Petr Vorel [this message]
2015-06-25 23:17 ` Arnout Vandecappelle
2015-06-30 21:11 ` Thomas Petazzoni
2015-07-01 10:07 ` Petr Vorel
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=20150624225647.GR28656@t61 \
--to=petr.vorel@gmail.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