From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rtai: remove option BR2_LINUX_KERNEL_EXT_RTAI_PATCH
Date: Tue, 21 Apr 2015 23:45:17 +0200 [thread overview]
Message-ID: <5536C4ED.3010008@mind.be> (raw)
In-Reply-To: <1429652188-11586-1-git-send-email-thomas.petazzoni@free-electrons.com>
On 21/04/15 23:36, Thomas Petazzoni wrote:
> This commit removes BR2_LINUX_KERNEL_EXT_RTAI_PATCH because this
> option never worked. It was added in commit
> 8797a9cd1fe6723db34b0c125d0d9d04e3483e8d, which added package/rtai/
> and RTAI as a Linux extension.
I agree with this change, however...
[snip]
> diff --git a/linux/Config.ext.in b/linux/Config.ext.in
> index c909254..ea79aa1 100644
> --- a/linux/Config.ext.in
> +++ b/linux/Config.ext.in
> @@ -44,12 +44,6 @@ config BR2_LINUX_KERNEL_EXT_RTAI
> help
> RTAI Kernel part.
>
> -config BR2_LINUX_KERNEL_EXT_RTAI_PATCH
> - depends on BR2_LINUX_KERNEL_EXT_RTAI
> - string "Path for RTAI patch file"
> - help
> - Optionally, explicitly specify the RTAI patch to use.
> -
This requires legacy handling. With in the help text something like
The BR2_LINUX_KERNEL_EXT_RTAI_PATCH option never worked, so it is
probably not useful. If you do have a valid use case and it used to
work for you, please let us know on buildroot at buildroot.net.
Regards,
Arnout
[snip]
--
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:[~2015-04-21 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 21:36 [Buildroot] [PATCH] rtai: remove option BR2_LINUX_KERNEL_EXT_RTAI_PATCH Thomas Petazzoni
2015-04-21 21:45 ` Arnout Vandecappelle [this message]
2015-04-21 21:47 ` Thomas Petazzoni
2015-04-21 21:59 ` Arnout Vandecappelle
2015-04-21 22:02 ` Yann E. MORIN
2015-04-21 22:02 ` Yann E. MORIN
2015-04-22 20:13 ` Thomas Petazzoni
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=5536C4ED.3010008@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 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.