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/next] qemu: add an option to enable user mode networking (SLIRP)
Date: Wed, 29 Aug 2018 22:04:38 +0200	[thread overview]
Message-ID: <20180829220438.5a5c71ce@windsurf> (raw)
In-Reply-To: <20180827201501.24224-1-casantos@datacom.com.br>

Hello,

On Mon, 27 Aug 2018 17:15:01 -0300, Carlos Santos wrote:
> User mode networking is a useful feature that does not depend on other
> packages. Add an option to enable it but keep it disabled by default,
> for backwards compatibility.
> 
> Signed-off-by: Carlos Santos <casantos@datacom.com.br>

I've applied to next, with some minor tweaks, see below.


> +config BR2_PACKAGE_QEMU_SLIRP
> +	bool "Keep user mode networking (SLIRP)"

I understand you want to use "Keep" because SLIRP is normally enabled
by default in Qemu, and enabling this option allows to "keep" it.

However, I don't think such details really need to surface up to the
Config.in option prompts, so I've changed "Keep" to "Enable".

Indeed, if the option is selected, SLIRP support is enabled, if the
option is not selected SLIRP support is disabled.

> +	help
> +	  Keep user mode network stack, which is the default networking

I've changed Keep to Enable here as well.


> +# There is no "--enable-slirp"
> +ifneq ($(BR2_PACKAGE_QEMU_SLIRP),y)

and used positive logic here:

ifeq ($(BR2_PACKAGE_QEMU_SLIRP),)

Applied to next with those changes. Thanks!

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

      reply	other threads:[~2018-08-29 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 20:15 [Buildroot] [PATCH/next] qemu: add an option to enable user mode networking (SLIRP) Carlos Santos
2018-08-29 20:04 ` Thomas Petazzoni [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=20180829220438.5a5c71ce@windsurf \
    --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