All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH 2/2] arago-test-image: fixes for RAMDISK usage
Date: Mon, 1 Jul 2013 14:55:37 -0400	[thread overview]
Message-ID: <20130701185537.GA4941@edge> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED1015962C5BA@DLEE11.ent.ti.com>

On Mon, Jul 01, 2013 at 05:52:32PM +0000, Maupin, Chase wrote:
> >-----Original Message-----
> >From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> >bounces@arago-project.org] On Behalf Of Denys Dmytriyenko
> >Sent: Monday, July 01, 2013 11:30 AM
> >To: meta-arago@arago-project.org
> >Subject: [meta-arago] [PATCH 2/2] arago-test-image: fixes for
> >RAMDISK usage
> >
> >From: Denys Dmytriyenko <denys@ti.com>
> >
> >* Build tar.gz and ext2.gz - good for RAMDISK/SD/NFS
> >* Relax compatibility list to be generic
> >* Remove large multimedia packagegroup to better fit into RAM
> >
> 
> Why not squash this with the previous patch?

The first patch was from Carlos, so I didn't want to hack it up right away so 
he gets a proper credit... But I guess I can squash them and mention that in 
the commit message...


> >Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> >Cc: Carlos Hernandez <ceh@ti.com>
> >---
> > meta-arago-distro/recipes-core/images/arago-test-image.bb | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> >diff --git a/meta-arago-distro/recipes-core/images/arago-test-
> >image.bb b/meta-arago-distro/recipes-core/images/arago-test-
> >image.bb
> >index 49e5a8d..403041f 100644
> >--- a/meta-arago-distro/recipes-core/images/arago-test-image.bb
> >+++ b/meta-arago-distro/recipes-core/images/arago-test-image.bb
> >@@ -5,14 +5,13 @@ LIC_FILES_CHKSUM =
> >"file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3
> >
> > require arago-image.inc
> >
> >-COMPATIBLE_MACHINE =
> >"omap3|dm365|omapl138|ti813x|ti814x|ti816x|omap4|ti33x"
> >+IMAGE_FSTYPES = "tar.gz ext2.gz"
> >
> > IMAGE_INSTALL += "\
> >     packagegroup-arago-base \
> >     packagegroup-arago-console \
> >     packagegroup-arago-base-tisdk \
> >     packagegroup-arago-tisdk-crypto \
> >-    packagegroup-arago-tisdk-multimedia \
> >     packagegroup-arago-tisdk-addons \
> >     packagegroup-arago-test \
> >     packagegroup-arago-test-addons \
> >--
> >1.8.2.1
> >
> >_______________________________________________
> >meta-arago mailing list
> >meta-arago@arago-project.org
> >http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


  reply	other threads:[~2013-07-01 18:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 16:30 [PATCH 1/2] arago-test: define system test packagegroup and image Denys Dmytriyenko
2013-07-01 16:30 ` [PATCH 2/2] arago-test-image: fixes for RAMDISK usage Denys Dmytriyenko
2013-07-01 17:52   ` Maupin, Chase
2013-07-01 18:55     ` Denys Dmytriyenko [this message]
2013-07-01 17:52 ` [PATCH 1/2] arago-test: define system test packagegroup and image Maupin, Chase

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=20130701185537.GA4941@edge \
    --to=denys@ti.com \
    --cc=chase.maupin@ti.com \
    --cc=meta-arago@arago-project.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.