Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] qemu: fix host virtfs option
Date: Thu, 1 Aug 2019 18:02:39 +0200	[thread overview]
Message-ID: <20190801180239.262e5f6e@windsurf.home> (raw)
In-Reply-To: <20190801092701.8766-1-vincent.stehle@arm.com>

Hello Vincent,

On Thu,  1 Aug 2019 11:27:01 +0200
Vincent Stehl? <vincent.stehle@arm.com> wrote:

> Fix the build of host-qemu with virtfs enabled: fix a typo in makefile
> conditional and add a dependency on host-libcap.
> 
> The virtfs configuration option was added by commit e0f49e648401
> ("package/qemu: add option to enable virtual filesystem in host qemu").
> 
> Signed-off-by: Vincent Stehl? <vincent.stehle@arm.com>
> Cc: Etienne Carriere <etienne.carriere@linaro.org>
> ---
> 
> 
> Hi,
> 
> I build-tested this with a number of architectures[1], with VIRTFS=y/n and
> this looks fine.
>   During testing I remarked that VIRTFS=n is somewhat "weak", as it does
> not forcibly disable virtfs. This means qemu can still auto-detect libcap
> and libattr, and decide to auto-enable virtfs. I think this does not harm,
> but we could also add an explicit --disable-virtfs if preferred. Do not
> hesitate to let me know if I should respin with this change.

Yes, we like to explicitly disable features, when possible.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-08-01 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01  9:27 [Buildroot] [PATCH 1/1] qemu: fix host virtfs option Vincent Stehlé
2019-08-01 16:02 ` Thomas Petazzoni [this message]
2019-08-01 17:09   ` [Buildroot] [PATCH v2] " Vincent Stehlé
2019-08-01 17:55     ` Peter Korsgaard
2019-08-21 12:38     ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2019-08-01 11:57 [Buildroot] [PATCH 1/1] " Vincent Stehlé
2019-08-02  9:18 ` Etienne Carriere

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=20190801180239.262e5f6e@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --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