From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] [RFC] platform: update galileo to 3.14 kernel
Date: Mon, 22 Aug 2016 15:46:56 +0300 [thread overview]
Message-ID: <1471870016.4887.210.camel@linux.intel.com> (raw)
In-Reply-To: <1471868735-13766-1-git-send-email-padraig.connolly@intel.com>
On Mon, 2016-08-22 at 13:25 +0100, Padraig James Connolly wrote:
> Updating kernel for Galileo board BSP from 3.8 to 3.14
> ?*Changed board defconfig to pull new 3.14 kernel
> ?*New kernel config file for 3.14 kernel
> ?*Changed defconfig to use new kernel config
> ?*Removed old 3.8 kernel config
What is not working with the upstream kernel?
Btw, we are preparing some common infrastructure for Intel boards for
Buildroot (*), it would be nice to re-integrate Galileo there as well.
(*) Will be published at some point later when we have done some
testing, though seems you are working for Intel, so, we can show you
this earlier.
>
> ?Signed-off-by: Padraig Connolly <padraig.connolly@intel.com>
> ---
> ?board/intel/galileo/linux-3.14.config | 308
> ++++++++++++++++++++++++++++++++++
> ?board/intel/galileo/linux-3.8.config??| 307 -----------------------
> ----------
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-08-22 12:46 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 [this message]
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
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=1471870016.4887.210.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.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.