From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 9CB4FE00DEB; Fri, 16 Dec 2016 04:27:46 -0800 (PST) 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.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (ernstp[at]gmail.com) * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [209.85.161.196 listed in dnsbl.sorbs.net] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.161.196 listed in list.dnswl.org] Received: from mail-yw0-f196.google.com (mail-yw0-f196.google.com [209.85.161.196]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7A494E00DB0 for ; Fri, 16 Dec 2016 04:27:43 -0800 (PST) Received: by mail-yw0-f196.google.com with SMTP id b66so3790303ywh.2 for ; Fri, 16 Dec 2016 04:27:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bcN4SEGYdPh5KQwLtx2HzUp73p5f6zQmpGdoZbJW6NY=; b=MMQV6GMajHBKCtrw/2HM1t1dYCyurjubcC11DtZwzdR8GY0q0GuePMCWP/lOxYLne3 VaOkJagA1759jmzgmgVcnnvfde7oKuf0H0icLoYyMPV0fpEhF1CztWGSckEsd63nfyoQ 2QXbAfH0JUsaTIlGYqnlxfCtMEormBSORfKM43iCzhQ+v/xir2x7/M+JNOYtwb234LzK Fv8suOu2sc/yJAxvs23AAgTFzwr0XdqtvkXCLXLJgB1FdAdXlWXD9kex3qhHOME8Axo/ dsbXeL78oYxSpYPEi68naBgXRKeD+QpZjilbrhqgSCjv5x3eV9tpgqTikiO382WsoWz+ E6xA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bcN4SEGYdPh5KQwLtx2HzUp73p5f6zQmpGdoZbJW6NY=; b=Tn9gO0xOK9ZBQntQxcuOeYGaeA/nBAc2cbY9X9eegkm/Mc+hCS/+xI18fbLZ4DaQFC HX4uh0EuNPjBfUHIwoULzJlD+qaNygjR5Ru4/5PsJXSBMcEBvEkVavST5HLsZ9gJPzq8 JiWtiJLf8xzSdv0XmCrstG90jaSSZT7TbNbYIK7HgDpnSSUCDI4VNGrigf6wPMPoLUGJ 2dL8hpZExQksT8/9s2LDxulDkIVtYirP7DYS9AUe1lUTwK+9unIXmk1YHrdtg4FGGncS EVHCErEzhlsyBxQ5a25SibVKwS8yvjngyuVTDZDtlNHEhfydElI6yGLpbbc8QFxgqoi8 BMQg== X-Gm-Message-State: AKaTC00d5RwdoMN1v36IQfXNd+eua+BzZHZVFip+wenJ1dvTATPLHWWnxhwa0JizTlbovCvUDcPCZ7/WjJUMsw== X-Received: by 10.129.112.82 with SMTP id l79mr2098309ywc.222.1481891262431; Fri, 16 Dec 2016 04:27:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.1.139 with HTTP; Fri, 16 Dec 2016 04:27:42 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Ernst_Sj=C3=B6strand?= Date: Fri, 16 Dec 2016 13:27:42 +0100 Message-ID: To: =?UTF-8?Q?Richard_R=C3=B6jfors?= Cc: meta-freescale@yoctoproject.org Subject: Re: Is there any point in keeping linux-imx.inc? 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: Fri, 16 Dec 2016 12:27:46 -0000 Content-Type: multipart/alternative; boundary=94eb2c0b131a4b09c20543c5b277 --94eb2c0b131a4b09c20543c5b277 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, well I'm just saying that linux-fscl-imx is using the exact same code (SHA1:s even I would say!) as linux-imx, it's the same code in http://git.freescale.com/git/cgit.cgi/imx/linux-imx as in https://github.com/Freescale/linux-fslc/tree/4.1-2.0.x-imx So there's no point having any reference to http://git.freescale.com, and linux-fscl-imx.* makes linux-imx.inc and linux-imx_4.1.15.bb redundant. Regards //Ernst 2016-12-16 11:57 GMT+01:00 Richard R=C3=B6jfors = : > On Fri, Dec 16, 2016 at 9:56 AM, Ernst Sj=C3=B6strand = wrote: > > > > > > I'm trying to figure out the IMX/FSCL kernel branches and realized that > > linux-fscl-imx and linux-imx is the same thing. > > I don't realise the same thing. > > My view is: > -fslc- gets more stuff merged from upstreams and additional fixes brought > in. > > linux-imx is FSL/NXP's slowly progressing tree. Why are they not > trying to go mainline instead? > > --Richard > --94eb2c0b131a4b09c20543c5b277 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

well I'= m just saying that
linux-fscl-imx is using the exact same code (SH= A1:s even I would say!) as linux-imx,
it's the same code in http://git.fr= eescale.com/git/cgit.cgi/imx/linux-imx as in
https://github.com/Freescal= e/linux-fslc/tree/4.1-2.0.x-imx

So there's no point ha= ving any reference to http://git.frees= cale.com,
and linux-fscl-imx.* makes linux-imx.inc and linux-imx_4.1.15.bb redundant.

= Regards
//Ernst

2016-12-16 11:57 GMT+01:00 Richard R=C3=B6jfors <richard.rojfors@gmail.com>:
On Fri, Dec 16, 2016 at 9:56 AM, Ernst Sj=C3=B6strand &l= t;ernstp@gmail.com> wrote:
>
>
> I'm trying to figure out the IMX/FSCL kernel branches and realized= that
> linux-fscl-imx and linux-imx is the same thing.

I don't realise the same thing.

My view is:
-fslc- gets more stuff merged from upstreams and additional fixes brought i= n.

linux-imx is FSL/NXP's slowly progressing tree. Why are they not
trying to go mainline instead?

--Richard

--94eb2c0b131a4b09c20543c5b277--