mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] host-libslirp: should not have a prompt, but build it in ALLYES
Date: Fri, 24 Mar 2023 10:03:35 +0100	[thread overview]
Message-ID: <20230324090335.298799-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230317093356.1062758-1-rhi@pengutronix.de>

Thanks, applied as 48f2bbc97be95b4652b7cea056c65e62ff2ae3e5.

Michael

[sent from post-receive hook]

On Fri, 24 Mar 2023 10:03:35 +0100, Roland Hieber <rhi@pengutronix.de> wrote:
> It's in the hosttools_noprompt section after all, and this way it gets
> compile-tested in ALLYES builds.
> 
> Fixes: 81fbc066ec4975fbfd0f (2023-03-12, "libslirp: new package: user-mode networking library used by qemu")
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> Message-Id: <20230317093356.1062758-1-rhi@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/host-libslirp.in b/rules/host-libslirp.in
> index d0a9f211f89a..e61e2b64b05e 100644
> --- a/rules/host-libslirp.in
> +++ b/rules/host-libslirp.in
> @@ -2,6 +2,6 @@
>  
>  config HOST_LIBSLIRP
>  	tristate
> +	default y if ALLYES
>  	select HOST_GLIB
>  	select HOST_MESON
> -	prompt "libslirp"



      reply	other threads:[~2023-03-24  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 16:57 [ptxdist] [PATCH] host-libslirp: should not have a prompt Roland Hieber
2023-03-17  6:55 ` Michael Olbrich
2023-03-17  9:33   ` [ptxdist] [PATCH v2] host-libslirp: should not have a prompt, but build it in ALLYES Roland Hieber
2023-03-24  9:03     ` Michael Olbrich [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=20230324090335.298799-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@pengutronix.de \
    /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