From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 67FD0E0082F; Wed, 20 Aug 2014 16:04:54 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [207.46.163.183 listed in list.dnswl.org] * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0183.outbound.protection.outlook.com [207.46.163.183]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9551EE007FE for ; Wed, 20 Aug 2014 16:04:51 -0700 (PDT) Received: from DM2PR0301MB0704.namprd03.prod.outlook.com (25.160.97.12) by DM2PR0301MB0893.namprd03.prod.outlook.com (25.160.216.143) with Microsoft SMTP Server (TLS) id 15.0.1015.17; Wed, 20 Aug 2014 23:04:47 +0000 Received: from DM2PR0301MB0701.namprd03.prod.outlook.com (25.160.96.27) by DM2PR0301MB0704.namprd03.prod.outlook.com (25.160.97.12) with Microsoft SMTP Server (TLS) id 15.0.995.14; Wed, 20 Aug 2014 23:04:45 +0000 Received: from DM2PR0301MB0701.namprd03.prod.outlook.com ([25.160.96.27]) by DM2PR0301MB0701.namprd03.prod.outlook.com ([25.160.96.27]) with mapi id 15.00.0995.014; Wed, 20 Aug 2014 23:04:46 +0000 From: Lauren Post To: Alexander Holler , "meta-freescale@yoctoproject.org" Thread-Topic: [meta-freescale] i.MX 3.10.31-1.1.0_beta release - community feedback requested Thread-Index: AQHPuvmsv2CCk3uJlEiP3BD5hu1/QJvaHUmAgAACzAA= Date: Wed, 20 Aug 2014 23:04:45 +0000 Message-ID: References: <8f1e8166115a4a4381ded78a5536c001@BY2PR03MB379.namprd03.prod.outlook.com> <23db6296a5b24ce3accdde41476d7d6d@DM2PR0301MB0701.namprd03.prod.outlook.com> <53F52703.6090006@ahsoftware.de> In-Reply-To: <53F52703.6090006@ahsoftware.de> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.88.168.50] x-microsoft-antispam: BCL:0;PCL:0;RULEID:UriScan:; x-forefront-prvs: 03094A4065 x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(377454003)(5423002)(13464003)(199003)(189002)(95666004)(46102001)(83322001)(19580405001)(85306004)(2656002)(99286002)(81542001)(19580395003)(64706001)(86362001)(79102001)(15202345003)(74316001)(76576001)(107886001)(66066001)(93886004)(83072002)(105586002)(87936001)(74502001)(107046002)(54356999)(106356001)(101416001)(74662001)(108616004)(99396002)(21056001)(33646002)(92566001)(77096002)(76176999)(4396001)(81342001)(20776003)(80022001)(106116001)(77982001)(15975445006)(50986999)(31966008)(76482001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR0301MB0704; H:DM2PR0301MB0701.namprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; MIME-Version: 1.0 X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:; X-OriginatorOrg: freescale.com Subject: Re: i.MX 3.10.31-1.1.0_beta release - community feedback requested X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2014 23:04:54 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Our policy is to be at LTSI kernel which is 3.10.31 http://ltsi.linuxfound= ation.org/=20 -----Original Message----- From: Alexander Holler [mailto:holler@ahsoftware.de]=20 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 f= eedback 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 ve= rsion 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 mys= elf on top of 3.10.52, without any problems (took me around 15 minutes to s= olve 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 pr= ovide security fixes (besides bugfixes). So I don't really understand why a= bout 20 minor releases of maybe import fixes are ignored. Regards, Alexander Holler