From: Denys Dmytriyenko <denis@denix.org>
To: "André Draszik" <git@andred.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Fix build issues with fitimage
Date: Thu, 14 Dec 2017 19:18:07 -0500 [thread overview]
Message-ID: <20171215001807.GH9221@denix.org> (raw)
In-Reply-To: <1513250295.30397.73.camel@andred.net>
On Thu, Dec 14, 2017 at 11:18:15AM +0000, André Draszik wrote:
> On Wed, 2017-12-13 at 18:23 -0800, Manjukumar Matha wrote:
> > While building fitimage with initramfs bundle using INITRAMFS_IMAGE and
> > INITRAMFS_IMAGE_BUNDLE = "1", we have few failures
>
> Nothing against these patches, but what is the use-case to do that? Why
> don't you just disable INITRAMFS_IMAGE_BUNDLE?
+1 here
Also, I don't think this is the first revision of the patch here, so please
specify [PATCH vX] accordingly, with log of changes between revisions.
--
Denys
next prev parent reply other threads:[~2017-12-15 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 2:23 [PATCH 0/2] Fix build issues with fitimage Manjukumar Matha
2017-12-14 2:23 ` [PATCH 1/2] kernel.bbclass: Fix fitimage build failure Manjukumar Matha
2017-12-14 2:23 ` [PATCH 2/2] kernel.bbclass: Fix fitimage deploy errors Manjukumar Matha
2017-12-14 11:18 ` [PATCH 0/2] Fix build issues with fitimage André Draszik
2017-12-15 0:18 ` Denys Dmytriyenko [this message]
2017-12-15 0:56 ` Manjukumar Harthikote Matha
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=20171215001807.GH9221@denix.org \
--to=denis@denix.org \
--cc=git@andred.net \
--cc=openembedded-core@lists.openembedded.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