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 17:26:53 +0000 [thread overview]
Message-ID: <1479144361.4408.75.camel@synopsys.com> (raw)
In-Reply-To: <20161114171516.GB3399@free.fr>
Hi Yann,
On Mon, 2016-11-14 at 18:15 +0100, Yann E. MORIN wrote:
> Alexey, All,
>
> On 2016-11-14 14:46 +0000, Alexey Brodkin spake thusly:
> [--SNIP--]
> >
> > The point is we were sitting on the patch for quite some time and when we saw
> > RC1 was cut (as always unexpectedly :)) simply sent out what we had in our tree.
>
> "Unexpectedly" is a bit of untrue: we've been doing releases every three
> months since February 2009, 7 years ago, with a one-month freeze before
> the release.
>
> So, anything that comes on-or-after the first day of the release month is
> not guaranteed to go in master, unless it is a fix.
>
> This is far from "unexpected". ;-)
I think you understood my sarcasm.
Frankly on my first submission of defconfigs for ARC boards I intentionally left
kernel version unspecified, i.e. the most recent kernel in BR was used
implicitly there. The reason was to stick to latest because all development
for ARC happens upstream and there's really no reason to use anything except
latest stable.
Well I may foresee very rare situations when latest stable is broken for us and so we
will urgently change version... but usually that's not the case.
Instead now we have to bump kernel version either every month so users of BR from
its master branch use latest kernel or at least right before RC1 so we have latest
in the release... IMHO that's a bit of overhead.
I'm not sure if described approach makes sense for many defconfigs in BR,
probably this is only ARC issue but I'd prefer it to be solved in some
"automated" way instead of following:
?a) Bumps in stable repo and then
?b) Bumps of default kernel version in BR
Any thoughts?
-Alexey
prev parent reply other threads:[~2016-11-14 17:26 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
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 [this message]
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=1479144361.4408.75.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