From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id E9B51E00848; Sun, 8 Feb 2015 03:05:28 -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=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -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 Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9640FE007AB for ; Sun, 8 Feb 2015 03:05:22 -0800 (PST) Received: from [192.168.0.40] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id 28F9F6000357; Sun, 8 Feb 2015 13:05:20 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1423393520; bh=XQWH5XYS4EevOKcMSFMicvPvUZ0WNpwehsZJ6KiraLA=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=/MWuwAy5nwDojOTS1jY4gFonlWsLcRgSDyoRvAAfPHJo8BVA4s+uR6g/LXaxWn74/ serUAnT5RY4Lk71OYamY9m9ONDytUtEmJnChTp4+NAKgMu7iUuRI53p2rID+OF8TJ7 TrgqvWtk2RDerp8pBLT4Lx8YhMnxUw/Xx6lI8R80= Message-ID: <54D742EF.8010307@mail.bg> Date: Sun, 08 Feb 2015 13:05:19 +0200 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0 MIME-Version: 1.0 To: Otavio Salvador References: <1423232976-23141-1-git-send-email-picmaster@mail.bg> <20150206154851.67df3156@e6520eb.localdomain> <54D4DBBE.1080505@mail.bg> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-arm][PATCH] linux-imx: Disable imx6sl code when not needed (3.10.17) 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: Sun, 08 Feb 2015 11:05:29 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Otavio, On 02/06/2015 05:51 PM, Otavio Salvador wrote: > Hello, > > On Fri, Feb 6, 2015 at 1:20 PM, Nikolay Dimitrov wrote: >> Hi Eric, >> >> On 02/06/2015 04:48 PM, Eric Bénard wrote: >>> >>> Hi Nikolay, >>> >>> Le Fri, 6 Feb 2015 16:29:36 +0200, >>> picmaster@mail.bg a écrit : >>> >>>> From: Nikolay Dimitrov >>>> >>>> >>>> Signed-off-by: Nikolay Dimitrov >>>> --- >>>> ...Disable-imx6sl-specific-code-when-imx6sl-.patch | 419 >>>> ++++++++++++++++++++ >>>> 1 file changed, 419 insertions(+) >>>> create mode 100644 >>>> recipes-kernel/linux/linux-imx-3.10.17/0002-ARM-imx6sl-Disable-imx6sl-specific-code-when-imx6sl-.patch >>>> >>>> diff --git >>>> a/recipes-kernel/linux/linux-imx-3.10.17/0002-ARM-imx6sl-Disable-imx6sl-specific-code-when-imx6sl-.patch >>>> b/recipes-kernel/linux/linux-imx-3.10.17/0002-ARM-imx6sl-Disable-imx6sl-specific-code-when-imx6sl-.patch >>>> new file mode 100644 >>>> index 0000000..3255352 >>>> --- /dev/null >>>> +++ >>>> b/recipes-kernel/linux/linux-imx-3.10.17/0002-ARM-imx6sl-Disable-imx6sl-specific-code-when-imx6sl-.patch >>>> @@ -0,0 +1,419 @@ >>>> +From 351f605f08b7fb808ed3fdcb57f61db478be2c59 Mon Sep 17 00:00:00 2001 >>>> +From: Nikolay Dimitrov >>>> +Date: Fri, 6 Feb 2015 14:37:50 +0200 >>>> +Subject: [PATCH] ARM: imx6sl: Disable imx6sl-specific code when imx6sl >>>> SOC >>>> + support is disabled >>>> + >>> >>> why is that needed ? >> >> >> The patch purpose is to handle enabling/disabling CONFIG_SOC_IMX6SL. >> Until now it wasn't possible due to some hard-coded pieces here and >> there (build fails when imx6sl support is disabled). > > Add this in the patch itself. > > Also, add this on the recipe and do a proper commit log for it as well. > > This helps to get this reviewed, merged and ease the handling of it in future. Thanks for your comments. V2 is on the way. > Did you check if 3.10.53 also needs this? Nope, as I can't test it easily. If someone volunteers to test the patch there, I can submit it. Regards, Nikolay