All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manjukumar Harthikote Matha <MANJUKUM@xilinx.com>
To: "Denys Dmytriyenko" <denis@denix.org>, "André Draszik" <git@andred.net>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Fix build issues with fitimage
Date: Fri, 15 Dec 2017 00:56:03 +0000	[thread overview]
Message-ID: <BL2PR02MB216331BD46CFE7E332C0354CB90B0@BL2PR02MB2163.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20171215001807.GH9221@denix.org>



> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Denys Dmytriyenko
> Sent: Thursday, December 14, 2017 4:18 PM
> To: André Draszik <git@andred.net>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 0/2] Fix build issues with fitimage
> 
> 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

Use case is to deploy fitimage (kernel image + rootfs +dtb) and (kernel image + rootfs) to meet backward compatibility of tools we distribute.

> 
> 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.
> 

Will do, there was no change in patch. Will add v2 on applicable patch

Thanks,
Manju


      reply	other threads:[~2017-12-15  0:56 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
2017-12-15  0:56     ` Manjukumar Harthikote Matha [this message]

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=BL2PR02MB216331BD46CFE7E332C0354CB90B0@BL2PR02MB2163.namprd02.prod.outlook.com \
    --to=manjukum@xilinx.com \
    --cc=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 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.