Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4 1/4] image.bbclass: fix dependency calculation when using conversion chaining
Date: Fri, 29 Jul 2016 11:22:09 +0300	[thread overview]
Message-ID: <20160729082209.GA32340@linux.intel.com> (raw)
In-Reply-To: <1469738564.9142.17.camel@linuxfoundation.org>

On Thu, Jul 28, 2016 at 09:42:44PM +0100, Richard Purdie wrote:
> On Wed, 2016-07-27 at 15:51 +0300, Ed Bartosh wrote:
> > From: Patrick Ohly <patrick.ohly@intel.com>
> > 
> > When using conversion chaining (for example example: .dsk.vdi.xz),
> > the imagetypes_getdepends() did not properly detect all compression
> > commands (thus skipping the corresponding COMPRESS_DEPENDS) and
> > the base type, leading to missing dependencies of the image's
> > do_rootfs
> > task.
> > 
> > This is not a big problem in practice because in those cases where
> > conversion chaining is useful (as in the example above), the missing
> > dependency is qemu-native, which typically gets built anyway.
> > 
> > imagetypes_getdepends() had hard-coded special treatment for certain
> > image types. This gets replaced with setting the normal IMAGE_DEPENDS
> > variables for these types.
> > 
> > [YOCTO #9076]
> > 
> > Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
> > Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> 
> This patch has come in multiple times and each time I look at it I ask
> that it be checked against changes that happened in parallel since I
> believe there is something "not right" in the merge. Its not an easy
> one to review as it makes several different kinds of changes.
> 
> I just spent a while comparing the changes and it removes the reference
> to IMAGE_FSTYPES_DEBUGFS so I do believe this patch *does* cause at
> least one regression. Whether there are other issues its really hard to
> say.
> 
> Can someone try and perhaps make the diff more obvious and split it up?
> 
Thank you for the review.

I'll try to split this patch later. For now I'm going to remove it from
the patchset.

--
Regards,
Ed


  reply	other threads:[~2016-07-29  8:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 12:51 [PATCH v4 0/4] image creation improvements Ed Bartosh
2016-07-27 12:51 ` [PATCH v4 1/4] image.bbclass: fix dependency calculation when using conversion chaining Ed Bartosh
2016-07-28 20:42   ` Richard Purdie
2016-07-29  8:22     ` Ed Bartosh [this message]
2016-07-28 20:51   ` Richard Purdie
2016-07-27 12:51 ` [PATCH v4 2/4] image creation: support converting masked types Ed Bartosh
2016-07-27 12:51 ` [PATCH v4 3/4] image.bbclass: rename COMPRESS(ION) to CONVERSION Ed Bartosh
2016-07-27 12:51 ` [PATCH v4 4/4] image.bbclass: prefer specialized image creation methods over chaining Ed Bartosh

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=20160729082209.GA32340@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox