From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: poky@yoctoproject.org, saul.wold@intel.com
Subject: Re: [PATCH 0/4][jethro] yocto-bsp related patches backported from master
Date: Wed, 3 Feb 2016 13:12:53 -0600 [thread overview]
Message-ID: <56B25135.6070203@linux.intel.com> (raw)
In-Reply-To: <86E97C86-4A71-4145-A22E-A61ECBA2EB7D@gmail.com>
On 02/03/2016 12:58 PM, Khem Raj wrote:
>> On Feb 3, 2016, at 9:08 AM, Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> wrote:
>>
>>
>>
>> On 02/03/2016 12:12 AM, Khem Raj wrote:
>>>> On Feb 2, 2016, at 2:50 AM, leonardo.sandoval.gonzalez@linux.intel.com wrote:
>>>>
>>>> From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
>>>>
>>>> Set of patches that mainly fixes the do_patch issues found when creating
>>>> BSP layers with the yocto-bsp tool. More detail on each patch description.
>>>>
>>> AUTOREV is going to set a bad example IMO, it will be better to translate auto rev
>>> into a static SHA value may be driven out of AUTOREV enquiry at the time of BSP layer
>>> creation.
>> On this series, I simple backported some yocto-bsp related patches into Jethro so I believe the patch remains valid.
>>
> OK fair enough.
>
>> In the other hand, you mean getting the SHA value from AUTOREV instead of using the AUTOREV variable? If yes, what would be the real benefit from it?
> AUTOREVs are good for development but eventually they are hard to use in a release products
> so setting a template to use AUTOREV can set a wrong pretext. We should not do that in default
> templates. If user chooses so be it.
Got it. I will elaborate a separate patch/series base on your comments.
Thanks.
>>>> Leonardo Sandoval (4):
>>>> yocto-bsp: Default kernel version to 4.1 on x86_64
>>>> yocto-bsp: Avoid duplication of user patches
>>>> ({{=machine}}-user-patches.scc)
>>>> yocto-bsp: Set KTYPE to user selected base branch
>>>> yocto-bsp: Set SRCREV meta/machine revisions to AUTOREV
>>>>
>>>> .../arch/arm/recipes-kernel/linux/files/machine-preempt-rt.scc | 3 ++-
>>>> .../arch/arm/recipes-kernel/linux/files/machine-standard.scc | 3 ++-
>>>> .../target/arch/arm/recipes-kernel/linux/files/machine-tiny.scc | 3 ++-
>>>> .../target/arch/arm/recipes-kernel/linux/linux-yocto-dev.bbappend | 1 -
>>>> .../arch/arm/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend | 6 +++---
>>>> .../arch/arm/recipes-kernel/linux/linux-yocto-tiny_3.14.bbappend | 6 +++---
>>>> .../arch/arm/recipes-kernel/linux/linux-yocto-tiny_3.19.bbappend | 6 +++---
>>>> .../arch/arm/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend | 6 +++---
>>>> .../target/arch/arm/recipes-kernel/linux/linux-yocto_3.14.bbappend | 7 +++----
>>>> .../target/arch/arm/recipes-kernel/linux/linux-yocto_3.19.bbappend | 7 +++----
>>>> .../target/arch/arm/recipes-kernel/linux/linux-yocto_4.1.bbappend | 7 +++----
>>>> .../arch/i386/recipes-kernel/linux/files/machine-preempt-rt.scc | 3 ++-
>>>> .../arch/i386/recipes-kernel/linux/files/machine-standard.scc | 3 ++-
>>>> .../target/arch/i386/recipes-kernel/linux/files/machine-tiny.scc | 3 ++-
>>>> .../target/arch/i386/recipes-kernel/linux/linux-yocto-dev.bbappend | 1 -
>>>> .../arch/i386/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend | 6 +++---
>>>> .../arch/i386/recipes-kernel/linux/linux-yocto-tiny_3.14.bbappend | 6 +++---
>>>> .../arch/i386/recipes-kernel/linux/linux-yocto-tiny_3.19.bbappend | 6 +++---
>>>> .../arch/i386/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend | 6 +++---
>>>> .../arch/i386/recipes-kernel/linux/linux-yocto_3.14.bbappend | 7 +++----
>>>> .../arch/i386/recipes-kernel/linux/linux-yocto_3.19.bbappend | 7 +++----
>>>> .../target/arch/i386/recipes-kernel/linux/linux-yocto_4.1.bbappend | 7 +++----
>>>> .../arch/mips/recipes-kernel/linux/files/machine-preempt-rt.scc | 3 ++-
>>>> .../arch/mips/recipes-kernel/linux/files/machine-standard.scc | 3 ++-
>>>> .../target/arch/mips/recipes-kernel/linux/files/machine-tiny.scc | 3 ++-
>>>> .../target/arch/mips/recipes-kernel/linux/linux-yocto-dev.bbappend | 1 -
>>>> .../arch/mips/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend | 6 +++---
>>>> .../arch/mips/recipes-kernel/linux/linux-yocto-tiny_3.14.bbappend | 6 +++---
>>>> .../arch/mips/recipes-kernel/linux/linux-yocto-tiny_3.19.bbappend | 6 +++---
>>>> .../arch/mips/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend | 6 +++---
>>>> .../arch/mips/recipes-kernel/linux/linux-yocto_3.14.bbappend | 7 +++----
>>>> .../arch/mips/recipes-kernel/linux/linux-yocto_3.19.bbappend | 7 +++----
>>>> .../target/arch/mips/recipes-kernel/linux/linux-yocto_4.1.bbappend | 7 +++----
>>>> .../arch/mips64/recipes-kernel/linux/files/machine-preempt-rt.scc | 3 ++-
>>>> .../arch/mips64/recipes-kernel/linux/files/machine-standard.scc | 3 ++-
>>>> .../target/arch/mips64/recipes-kernel/linux/files/machine-tiny.scc | 3 ++-
>>>> .../arch/mips64/recipes-kernel/linux/linux-yocto-dev.bbappend | 1 -
>>>> .../arch/mips64/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend | 6 +++---
>>>> .../mips64/recipes-kernel/linux/linux-yocto-tiny_3.14.bbappend | 6 +++---
>>>> .../mips64/recipes-kernel/linux/linux-yocto-tiny_3.19.bbappend | 6 +++---
>>>> .../arch/mips64/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend | 6 +++---
>>>> .../arch/mips64/recipes-kernel/linux/linux-yocto_3.14.bbappend | 5 ++---
>>>> .../arch/mips64/recipes-kernel/linux/linux-yocto_3.19.bbappend | 7 +++----
>>>> .../arch/mips64/recipes-kernel/linux/linux-yocto_4.1.bbappend | 7 +++----
>>>> .../arch/powerpc/recipes-kernel/linux/files/machine-preempt-rt.scc | 3 ++-
>>>> .../arch/powerpc/recipes-kernel/linux/files/machine-standard.scc | 3 ++-
>>>> .../arch/powerpc/recipes-kernel/linux/files/machine-tiny.scc | 3 ++-
>>>> .../arch/powerpc/recipes-kernel/linux/linux-yocto-dev.bbappend | 1 -
>>>> .../arch/powerpc/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend | 6 +++---
>>>> .../powerpc/recipes-kernel/linux/linux-yocto-tiny_3.14.bbappend | 6 +++---
>>>> .../powerpc/recipes-kernel/linux/linux-yocto-tiny_3.19.bbappend | 6 +++---
>>>> .../powerpc/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend | 6 +++---
>>>> .../arch/powerpc/recipes-kernel/linux/linux-yocto_3.14.bbappend | 7 +++----
>>>> .../arch/powerpc/recipes-kernel/linux/linux-yocto_3.19.bbappend | 7 +++----
>>>> .../arch/powerpc/recipes-kernel/linux/linux-yocto_4.1.bbappend | 7 +++----
>>>> .../arch/qemu/recipes-kernel/linux/files/machine-preempt-rt.scc | 3 ++-
>>>> .../arch/qemu/recipes-kernel/linux/files/machine-standard.scc | 3 ++-
>>>> .../target/arch/qemu/recipes-kernel/linux/files/machine-tiny.scc | 3 ++-
>>>> .../target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend | 1 -
>>>> .../arch/qemu/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend | 6 +++---
>>>> .../arch/qemu/recipes-kernel/linux/linux-yocto-tiny_3.14.bbappend | 6 +++---
>>>> .../arch/qemu/recipes-kernel/linux/linux-yocto-tiny_3.19.bbappend | 6 +++---
>>>> .../arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend | 6 +++---
>>>> .../arch/qemu/recipes-kernel/linux/linux-yocto_3.14.bbappend | 7 +++----
>>>> .../arch/qemu/recipes-kernel/linux/linux-yocto_3.19.bbappend | 7 +++----
>>>> .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.1.bbappend | 7 +++----
>>>> .../arch/x86_64/recipes-kernel/linux/files/machine-preempt-rt.scc | 3 ++-
>>>> .../arch/x86_64/recipes-kernel/linux/files/machine-standard.scc | 3 ++-
>>>> .../target/arch/x86_64/recipes-kernel/linux/files/machine-tiny.scc | 3 ++-
>>>> .../target/arch/x86_64/recipes-kernel/linux/kernel-list.noinstall | 2 +-
>>>> .../arch/x86_64/recipes-kernel/linux/linux-yocto-dev.bbappend | 1 -
>>>> .../arch/x86_64/recipes-kernel/linux/linux-yocto-rt_3.14.bbappend | 6 +++---
>>>> .../x86_64/recipes-kernel/linux/linux-yocto-tiny_3.14.bbappend | 6 +++---
>>>> .../x86_64/recipes-kernel/linux/linux-yocto-tiny_3.19.bbappend | 6 +++---
>>>> .../arch/x86_64/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend | 6 +++---
>>>> .../arch/x86_64/recipes-kernel/linux/linux-yocto_3.14.bbappend | 7 +++----
>>>> .../arch/x86_64/recipes-kernel/linux/linux-yocto_3.19.bbappend | 7 +++----
>>>> .../arch/x86_64/recipes-kernel/linux/linux-yocto_4.1.bbappend | 7 +++----
>>>> 78 files changed, 189 insertions(+), 196 deletions(-)
>>>>
>>>> --
>>>> 2.6.2
>>>>
>>>> --
>>>> _______________________________________________
>>>> poky mailing list
>>>> poky@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2016-02-03 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 10:50 [PATCH 0/4][jethro] yocto-bsp related patches backported from master leonardo.sandoval.gonzalez
2016-02-02 10:50 ` [PATCH 1/4][jethro] yocto-bsp: Default kernel version to 4.1 on x86_64 leonardo.sandoval.gonzalez
2016-02-02 10:50 ` [PATCH 2/4][jethro] yocto-bsp: Avoid duplication of user patches ({{=machine}}-user-patches.scc) leonardo.sandoval.gonzalez
2016-02-02 10:50 ` [PATCH 3/4][jethro] yocto-bsp: Set KTYPE to user selected base branch leonardo.sandoval.gonzalez
2016-02-02 10:50 ` [PATCH 4/4][jethro] yocto-bsp: Set SRCREV meta/machine revisions to AUTOREV leonardo.sandoval.gonzalez
2016-02-03 6:12 ` [PATCH 0/4][jethro] yocto-bsp related patches backported from master Khem Raj
2016-02-03 17:08 ` Leonardo Sandoval
2016-02-03 18:58 ` Khem Raj
2016-02-03 19:12 ` Leonardo Sandoval [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 10:25 leonardo.sandoval.gonzalez
2016-02-02 18:54 ` Leonardo Sandoval
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=56B25135.6070203@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.com \
--cc=saul.wold@intel.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.