All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Adami <andrea.adami@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Simplify the creation of cramfs images
Date: Fri, 30 Aug 2013 01:23:18 +0200	[thread overview]
Message-ID: <cover.1377818011.git.andrea.adami@gmail.com> (raw)

Extending the util-linux recipe allows the creation
of cramfs images with tools contained in oe-core.

The cramfs recipe in meta-filesystems will be removed
so there will be any conflict nor replacement of
cramfs-native.

This fixes as well an HOB bug (missing helper for cramfs).

Andrea Adami (2):
  util-linux: package mkfs.cramfs and fsck.cramfs
  image_types.bbclass: use mkfs.cramfs instead of makecramfs

 meta/classes/image_types.bbclass            | 4 ++--
 meta/recipes-core/util-linux/util-linux.inc | 5 +++++
 2 files changed, 7 insertions(+), 2 deletions(-)

-- 
1.8.1.5



             reply	other threads:[~2013-08-29 23:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 23:23 Andrea Adami [this message]
2013-08-29 23:23 ` [PATCH 1/2] util-linux: package mkfs.cramfs and fsck.cramfs Andrea Adami
2013-08-29 23:23 ` [PATCH 2/2] image_types.bbclass: use mkfs.cramfs instead of makecramfs Andrea Adami

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=cover.1377818011.git.andrea.adami@gmail.com \
    --to=andrea.adami@gmail.com \
    --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.