All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: "zhenhua.luo@freescale.com" <zhenhua.luo@freescale.com>,
	 "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-fsl-ppc][PATCH] linux-qoriq: Remove Altivec from T1040 64-bit defconfig
Date: Mon, 10 Nov 2014 18:44:40 -0500	[thread overview]
Message-ID: <54614DE8.8090604@mindchasers.com> (raw)
In-Reply-To: <e101442bb6a547bdab152da08b87c24e@CY1PR0301MB0715.namprd03.prod.outlook.com>

On 11/05/2014 05:17 AM, zhenhua.luo@freescale.com wrote:
> Bob,
>
> Since the kernel fragment patch is still under discussion.
>
> Please submit patch to append the kernel patch in kernel bb file.
>

Zhenhua and Otavio,

Please guide me on how I should submit multiple kernel patches for 
linux-qoriq that also require multiple SRC_URI line additions to the 
same linux-qoriq_3.12.bb file in the meta-fsl-ppc layer.

I have a few different kernel patches that I want to submit related to 
the T1040 (e.g., remove Altivec flag).  I'm ready to send a few now, and 
I expect to have one or two each week going forward.

Each patch addresses one problem and is self contained in its own kernel 
.patch file.

Should I send these as one email that contains multiple kernel patches 
plus a single patch to linux-qoriq_3.12.bb to include the SRC_URI 
additions?

Or maybe I should send each kernel patch out separately in its own email 
(like I have already done), wait for comments, and then combine them 
into one email patch submission that then bundles the 
linux-qoriq_3.12.bb patch.

Please let me know what you would like to see.

Thanks

Bob


>
> Best Regards,
>
> Zhenhua
>
>> -----Original Message-----
>> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
>> bounces@yoctoproject.org] On Behalf Of Bob Cochran
>> Sent: Saturday, November 01, 2014 5:21 AM
>> To: meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH] linux-qoriq: Remove
>> Altivec from T1040 64-bit defconfig
>>
>> Note that I didn't address patching the meta-fsl-ppc metadata (e.g., adding
>> patch to SRC_URI) since there is a meta-data patch from Zongchun still pending
>> regarding the support of scc files.
>>
>> Unless I am directed otherwise, I'll just keep sending up the kernel patches by
>> themselves.
>>
>> Bob
>>
>>
>> On 10/31/2014 05:05 PM, Bob Cochran wrote:
>>> T1040 uses an E5500 processor, and E5500 doesn't have an Altivec unit
>>>
>>> Signed-off-by: Bob Cochran <yocto@mindchasers.com>
>>> ---
>>>    arch/powerpc/configs/t1040_64bit_smp_defconfig |    2 +-
>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/powerpc/configs/t1040_64bit_smp_defconfig
>>> b/arch/powerpc/configs/t1040_64bit_smp_defconfig
>>> index 1b987d9..c2005f2 100644
>>> --- a/arch/powerpc/configs/t1040_64bit_smp_defconfig
>>> +++ b/arch/powerpc/configs/t1040_64bit_smp_defconfig
>>> @@ -1,6 +1,6 @@
>>>    CONFIG_PPC64=y
>>>    CONFIG_PPC_BOOK3E_64=y
>>> -CONFIG_ALTIVEC=y
>>> +# CONFIG_ALTIVEC is not set
>>>    CONFIG_SMP=y
>>>    CONFIG_NR_CPUS=24
>>>    CONFIG_SYSVIPC=y
>>>
>>
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>



  parent reply	other threads:[~2014-11-10 23:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 21:05 [meta-fsl-ppc][PATCH] linux-qoriq: Remove Altivec from T1040 64-bit defconfig Bob Cochran
2014-10-31 21:21 ` Bob Cochran
2014-11-05 10:17   ` zhenhua.luo
2014-11-06  0:57     ` Bob Cochran
2014-11-10 23:44     ` Bob Cochran [this message]
2014-11-11 11:02       ` Otavio Salvador
2014-11-11 18:53         ` Bob Cochran
2014-11-12 12:06           ` zhenhua.luo
2014-11-12 17:07             ` Bob Cochran

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=54614DE8.8090604@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=zhenhua.luo@freescale.com \
    /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.