All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mats Karrman <mats.dev.list@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [PATCH] fsl-kernel-localversion: Add preconfigure dependency on do_unpack
Date: Tue, 25 Apr 2017 22:28:08 +0200	[thread overview]
Message-ID: <f419096f-9bfa-f9c4-cefe-8bbea8c9c6d7@gmail.com> (raw)
In-Reply-To: <CAP9ODKom2VzL06jv1aRrmqo2vpEahu5qdt2Pi4iozqLev=9D1A@mail.gmail.com>

Hi Otavio,

On 04/25/2017 03:51 PM, Otavio Salvador wrote:

> Hello Mats,
>
> On Thu, Apr 13, 2017 at 12:33 PM, Mats Karrman <mats.dev.list@gmail.com> wrote:
>> From: Mats Karrman <mats@southpole.se>
>> Date: Thu, 13 Apr 2017 17:11:58 +0200
>> Subject: [PATCH] fsl-kernel-localversion: Add preconfigure dependency on
>> do_unpack
>>
>> Even if 'externalsrc' is used, SRC_URI may specify a 'defconfig'.
>> However as the use of 'externalsrc' will do away with the do_patch
>> task, do_preconfigure is in risk of being run before the defconfig
>> is copied to the build directory. This patch adds a second dependency
>> on 'do_unpack' that makes sure this does not happen.
> It does not apply on master; can you reproduce it on master? Use
> meta-freescale please.

I will try to do this shortly.

I haven't been active with Yocto for a while and totaly missed the
switch to (?) meta-freescale... Is there an announcement or something
you can point me to to put me on track?

BR // Mats



  reply	other threads:[~2017-04-25 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 15:33 [PATCH] fsl-kernel-localversion: Add preconfigure dependency on do_unpack Mats Karrman
2017-04-25 13:51 ` Otavio Salvador
2017-04-25 20:28   ` Mats Karrman [this message]
2017-04-25 20:35     ` Otavio Salvador

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=f419096f-9bfa-f9c4-cefe-8bbea8c9c6d7@gmail.com \
    --to=mats.dev.list@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio.salvador@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.