From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] config: bump linux kernel to 4.8.6 in synopsys defconfigs
Date: Mon, 14 Nov 2016 14:34:01 +0000 [thread overview]
Message-ID: <1479133987.4408.48.camel@synopsys.com> (raw)
In-Reply-To: <20161114150740.394bdd02@free-electrons.com>
Hi Thomas,
On Mon, 2016-11-14 at 15:07 +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 14 Nov 2016 12:32:29 +0000, Vlad Zakharov wrote:
>
> >
> > We apologize for coming late with that update.
> > But could you please apply it on master as it is important for us to come up with latest kernel in upcoming
> > Buildroot release.
> > Updated configs were build- and run tested on corresponding platforms, so there shouldn't be any regressions there.
>
> Once -rc1 has passed, we don't apply version bumps (be it to packages
> or defconfigs), unless they fix a specific issue.
>
> What is the issue with having this update part of 2017.02 ?
Obviously since we live in upstream everything that could not be applied to
stable branches (i.e. is not a trivial fix and longer than 200 lines) get
merged in newer kernels.
In particular following commit was not accepted in
backports:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=840c054fd0efb048df6fceb0c46385ec5b66dfe6
See discussion here?http://www.spinics.net/lists/stable/msg143544.html
The problem is in GCC v6.x newer ABI is used for ARCv2 and so only kernels v4.8+
will work. I.e. existing 4.7 will fail to run user-space apps built with GCC 6.x.
Indeed we may add mentioned off-the-tree patch in BR for 4.7 but I'd rather bump
kernel version here with which we get more fixes across the tree for our users.
-Alexey
next prev parent reply other threads:[~2016-11-14 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 15:53 [Buildroot] [PATCH] config: bump linux kernel to 4.8.6 in synopsys defconfigs Vlad Zakharov
2016-11-11 14:18 ` Thomas Petazzoni
2016-11-14 12:32 ` Vlad Zakharov
2016-11-14 14:07 ` Thomas Petazzoni
2016-11-14 14:34 ` Alexey Brodkin [this message]
2016-11-14 14:42 ` Thomas Petazzoni
2016-11-14 14:46 ` Alexey Brodkin
2016-11-14 15:14 ` Thomas Petazzoni
2016-11-14 17:15 ` Yann E. MORIN
2016-11-14 17:26 ` Alexey Brodkin
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=1479133987.4408.48.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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