From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: Add CIP SLTS easy selection option
Date: Fri, 3 Mar 2017 23:46:36 +0100 [thread overview]
Message-ID: <20170303234636.0dbf4fd6@free-electrons.com> (raw)
In-Reply-To: <1488577816-19047-1-git-send-email-angelo.compagnucci@gmail.com>
Hello,
On Fri, 3 Mar 2017 22:50:16 +0100, Angelo Compagnucci wrote:
> This patch adds an easy way to select the CIP project SLTS
> kernel within the kernel menu.
>
> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
I personally don't think we should have explicit support for kernels
other than the vanilla Linux kernel. Our kernel options already allow
to select any arbitrary tarball or Git repository, which makes it
possible to use this linux-cip Git repository as your kernel source if
you like it.
Supporting explicitly additional kernel trees is a never-ending story.
Everyone will want its own kernel tree listed in Buildroot.
And this linux-cip thing is in fact probably a lot less popular than
other non-vanilla kernel trees (like the one for RaspberryPi, for
BeagleoBone, the PREEMPT_RT tree, etc.).
So I apologize, but I'm personally not in favor of this patch.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-03 22:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 21:50 [Buildroot] [PATCH] linux: Add CIP SLTS easy selection option Angelo Compagnucci
2017-03-03 22:46 ` Thomas Petazzoni [this message]
2017-03-03 22:50 ` Arnout Vandecappelle
2017-03-03 23:02 ` Thomas Petazzoni
2017-03-03 23:43 ` Arnout Vandecappelle
2017-03-04 10:11 ` Thomas Petazzoni
2017-03-04 11:31 ` Angelo Compagnucci
2017-03-04 12:17 ` Arnout Vandecappelle
2017-03-04 14:08 ` Angelo Compagnucci
2017-03-04 14:12 ` Thomas Petazzoni
2017-03-04 14:38 ` Angelo Compagnucci
2017-03-04 14:42 ` Thomas Petazzoni
2017-03-04 15:07 ` Angelo Compagnucci
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=20170303234636.0dbf4fd6@free-electrons.com \
--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 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.