From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ian Geiser <geiseri@geekcentral.pub>
Cc: "<openembedded-core@lists.openembedded.org>"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Allow different filesystems to be used for VM images.
Date: Fri, 29 Apr 2016 12:10:47 +0100 [thread overview]
Message-ID: <1461928247.3166.1.camel@linuxfoundation.org> (raw)
In-Reply-To: <15461a3e2b1.db27b2f76194.3175716769885720576@geekcentral.pub>
On Fri, 2016-04-29 at 06:50 -0400, Ian Geiser wrote:
> ---- On Fri, 29 Apr 2016 04:19:00 -0400 Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote ----
> > On Thu, 2016-04-28 at 15:21 -0400, Ian Reinhart Geiser wrote:
> > > This allows for things like btrfs to be used vs just ext4.
> > > The default value of ext4 is kept so there is no functional
> > > change unless ROOTFS_TYPE is set in the inherting recipe.
> > >
> > > Signed-off-by: Ian Reinhart Geiser <geiseri@geekcentral.pub>
> > > ---
> > > meta/classes/image-vm.bbclass | 13 +++++++------
> > > 1 file changed, 7 insertions(+), 6 deletions(-)
> >
> >
> > This seems reasonable but could I ask you to use a variable name
> with
> > "VM" in the name please?
> >
> > I appreciate some of the existing ones don't do this but moving
> forward
> > we need to try and better namespace some of these class specific
> > variables and this seems like a good place to start.
> >
> > VM_ROOTFS_TYPE would be better for example (or VMIMG_ROOTFS_TYPE).
> >
> The other ones have foo_VM in the name. Would ROOTFS_TYPE_VM be
> acceptable?
I'd really prefer to try and use a prefix since otherwise its harder to
know this is from the VM class rather than the rootfs classes which
already heavily use ROOTFS_*...
Cheers,
Richard
prev parent reply other threads:[~2016-04-29 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 19:21 [PATCH] Allow different filesystems to be used for VM images Ian Reinhart Geiser
2016-04-29 8:19 ` Richard Purdie
2016-04-29 10:50 ` Ian Geiser
2016-04-29 11:10 ` Richard Purdie [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=1461928247.3166.1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=geiseri@geekcentral.pub \
--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