From: Alexander Holler <holler@ahsoftware.de>
To: Lauren Post <Lauren.Post@freescale.com>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: i.MX 3.10.31-1.1.0_beta release - community feedback requested
Date: Thu, 21 Aug 2014 01:29:24 +0200 [thread overview]
Message-ID: <53F52F54.2020102@ahsoftware.de> (raw)
In-Reply-To: <f35e11c7bb0d4693ac0a46ad45fc8ca0@DM2PR0301MB0701.namprd03.prod.outlook.com>
Am 21.08.2014 01:04, schrieb Lauren Post:
> Our policy is to be at LTSI kernel which is 3.10.31 http://ltsi.linuxfoundation.org/
Oh, another longterm stable tree. Thanks for enlighten me.
>
> -----Original Message-----
> From: Alexander Holler [mailto:holler@ahsoftware.de]
> Sent: Wednesday, August 20, 2014 5:54 PM
> To: Post Lauren-RAA013; meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] i.MX 3.10.31-1.1.0_beta release - community feedback requested
>
> Am 18.08.2014 17:32, schrieb Lauren Post:
>
> Hello,
>
> I'm new to i.MX6 and don't use yocto, so pelase forgive me if I ask a maybe stupid question.
>
>> - Kernel upgrade to 3.10.31
>
> 3.10.y is already at 3.10.52. Is there any reason why the current stable version of the longterm 3.10.y branch isn't used as a base?
>
> Because I've run into a problem with 3.10.17 which was fixed with
> v3.10.22 (december last year) I've recently rebased those 1200+ patches myself on top of 3.10.52, without any problems (took me around 15 minutes to solve 3 conflicts, testing excluded). So merging the current stable version of 3.10.y, if prefered, should be equally easy.
>
> My understanding of the stable trees is that they are especially used to provide security fixes (besides bugfixes). So I don't really understand why about 20 minor releases of maybe import fixes are ignored.
>
> Regards,
>
> Alexander Holler
>
next prev parent reply other threads:[~2014-08-20 23:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b82299f1e1374ceea2a54dc92a7edc83@DM2PR0301MB0701.namprd03.prod.outlook.com>
[not found] ` <8f1e8166115a4a4381ded78a5536c001@BY2PR03MB379.namprd03.prod.outlook.com>
2014-08-18 15:32 ` i.MX 3.10.31-1.1.0_beta release - community feedback requested Lauren Post
2014-08-18 15:54 ` Alfonso Tamés
2014-08-18 17:28 ` Eric Nelson
2014-08-18 19:35 ` Carlos Rafael Giani
2014-08-18 21:14 ` John Weber
2014-08-19 0:34 ` Alfonso Tamés
2014-08-19 2:32 ` Sébastien Taylor
2014-08-19 6:56 ` Carlos Rafael Giani
2014-08-19 13:59 ` Otavio Salvador
2014-08-19 15:55 ` Eric Nelson
2014-08-19 16:01 ` Carlos Rafael Giani
2014-08-19 16:22 ` Eric Nelson
2014-08-19 17:21 ` Otavio Salvador
2014-08-19 18:25 ` Eric Nelson
2014-08-19 17:24 ` Otavio Salvador
2014-08-19 18:44 ` Eric Nelson
2014-08-19 19:23 ` Lauren Post
2014-08-19 20:00 ` Otavio Salvador
2014-08-19 20:13 ` Eric Bénard
2014-08-19 20:20 ` John Weber
2014-08-20 13:31 ` Daiane Angolini
2014-08-20 17:32 ` Sébastien Taylor
2014-08-20 22:53 ` Alexander Holler
2014-08-20 23:04 ` Lauren Post
2014-08-20 23:29 ` Alexander Holler [this message]
2014-08-20 18:12 xxiao8
2014-08-20 19:41 ` Otavio Salvador
2014-08-20 23:11 ` xxiao8
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=53F52F54.2020102@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=Lauren.Post@freescale.com \
--cc=meta-freescale@yoctoproject.org \
/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.