All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-ppc][PATCH] linux-qoriq: Remove Altivec from T1040 64-bit defconfig
Date: Tue, 11 Nov 2014 13:53:29 -0500	[thread overview]
Message-ID: <54625B29.6020508@mindchasers.com> (raw)
In-Reply-To: <CAP9ODKqLU1OVvU_tB7W+7HjezYrKDBbFh-1OgcfY+BbMnoKhVA@mail.gmail.com>

On 11/11/2014 06:02 AM, Otavio Salvador wrote:
> Hello Bob,
>
> On Mon, Nov 10, 2014 at 9:44 PM, Bob Cochran <yocto@mindchasers.com> wrote:
>> 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.
>
> This is my opinion, so wait Zhenhua to comment on this as well...
>
> I think it is better to:
>
> * Have one commit for each patch which detailed explain the issue and
> includes the:
>
>    . kernel patch file (with Upstream-Status: Pending)
>    . modification for .bb to include it
>


Thanks for the reply Otavio.

So if I want to send multiple patches (each patch is a separate email 
that includes both the kernel patch & a patch for linux-qoriq_3.12.bb), 
then each patch of linux-qoriq_3.12.bb will depend on any of my 
previously submitted patches, right?

In other words, the SRC_URI in the linux-qoriq_3.12.bb patch will show 
my prior kernel patch submissions regardless of whether they have been 
merged / approved.

Example: (assume that "configure-T1040-for-FMAN-3VL.patch" was 
previously submitted but not yet approved / merged) -


...
 
file://Fix-CVE-2014-5077-sctp-inherit-auth-capable-on-INIT-collisions.patch 
\
     file://Fix-CVE-2014-5471_CVE-2014-5472.patch \
     file://configure-T1040-for-FMAN-V3L.patch   \
     +file://remove-Altivec-from-T1040-64-bit-defconfig.patch \
"
SRCREV = "c29fe1a733308cbe592b3af054a97be1b91cf2dd"





  reply	other threads:[~2014-11-11 18:53 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
2014-11-11 11:02       ` Otavio Salvador
2014-11-11 18:53         ` Bob Cochran [this message]
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=54625B29.6020508@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.