Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] iso9660: Added support for overlay directories
Date: Mon, 17 Feb 2014 13:02:37 +0100	[thread overview]
Message-ID: <5301FA5D.400@mind.be> (raw)
In-Reply-To: <20140217054228.20297e71@core2quad.morethan.org>

On 17/02/14 12:42, Mike Zick wrote:
> On Mon, 17 Feb 2014 08:06:17 +0100
> Arnout Vandecappelle <arnout@mind.be> wrote:
> 
>> On 04/02/14 22:25, Martin Bark wrote:
>>> This patch adds a variable BR2_TARGET_ROOTFS_ISO9660_OVERLAY that
>>> is similar to BR2_ROOTFS_OVERLAY except the files are placed in the
>>> iso9660 file system.
>>>
>>
> 
> Since Buildroot only builds root filesystems for the target device,
> it would probably be safe to drop the "TARGET_" distinction from
> that variable name.

 Agreed, but that should not be done in this patch. All the rootfs stuff
is currently using the BR2_TARGET_ROOTFS_ prefix, so this patch should
stick with that convention.

 Regards,
 Arnout

> 
> Mike
> 
>>> Signed-off-by: Martin Bark <martin@barkynet.com>  
>>
>> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
>>
>>  I haven't tried it but it looks obviously-correct.
> 
> 
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-02-17 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 21:25 [Buildroot] [PATCH 1/1] iso9660: Added support for overlay directories Martin Bark
2014-02-17  7:06 ` Arnout Vandecappelle
2014-02-17 11:42   ` Mike Zick
2014-02-17 12:02     ` Arnout Vandecappelle [this message]
2014-02-18 18:18   ` Martin Bark
2014-02-27 18:13     ` Jean Sorgemoel
2014-03-01 20:59       ` jean.sorgemoel at laposte.net

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=5301FA5D.400@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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