From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] [RFC] platform: update galileo to 3.14 kernel
Date: Tue, 23 Aug 2016 11:25:31 +0200 [thread overview]
Message-ID: <20160823112531.13f75bab@free-electrons.com> (raw)
In-Reply-To: <E704BB48EC9FDF4FA0A7A278C2546ACFE25B11@irsmsx105.ger.corp.intel.com>
Hello,
On Tue, 23 Aug 2016 08:05:15 +0000, Connolly, Padraig wrote:
> Could you elaborate on this preference please, in the previous
> version for the Galileo the defconfig pulled the kernel in a similar
> way I have done. The future plan is once everything is approved, we
> will update R. Kinsella's repo with the 3.14 kernel and the defconfig
> will pull from there instead of mine as it did before. I'm only
> using my repo as a temp for working on.
It's pretty simple:
- If a platform has reasonable support in the mainline Linux kernel,
then we prefer if our defconfigs use the mainline Linux kernel. By
"reasonable" support, I mean support with sufficient features for
the platform to actually be useful.
- If a platform doesn't have reasonable support in the mainline Linux
kernel, then we accept defconfigs that use other Linux kernel trees
(from vendors, or community maintained, etc.).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-23 9:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 12:25 [Buildroot] [PATCH] [RFC] platform: update galileo to 3.14 kernel Padraig James Connolly
2016-08-22 12:46 ` Andy Shevchenko
2016-08-22 12:54 ` Andy Shevchenko
2016-08-22 13:54 ` Connolly, Padraig
2016-08-22 14:33 ` Thomas Petazzoni
2016-08-23 8:05 ` Connolly, Padraig
2016-08-23 9:25 ` Thomas Petazzoni [this message]
2016-08-29 10:20 ` Connolly, Padraig
2016-08-29 11:15 ` Kinsella, Ray
2016-08-29 11:19 ` Thomas Petazzoni
2016-08-29 12:32 ` Connolly, Padraig
2016-08-29 12:48 ` Andy Shevchenko
2016-08-29 13:14 ` Kinsella, Ray
2016-08-29 13:52 ` Andy Shevchenko
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=20160823112531.13f75bab@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.