From: Bruce Rogers <brogers@suse.com>
To: Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: marcandre.lureau@redhat.com,
"Daniel P.Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] meson: install ivshmem-client and ivshmem-server
Date: Fri, 04 Sep 2020 05:49:28 -0600 [thread overview]
Message-ID: <5636584a23452c45d91f535e77374c37aaadcb48.camel@suse.com> (raw)
In-Reply-To: <87lfhpaofy.fsf@dusky.pond.sub.org>
On Fri, 2020-09-04 at 11:20 +0200, Markus Armbruster wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
> > On 04/09/20 09:24, Markus Armbruster wrote:
> > > > Ah, via the tools variable in configure. Nice maze. I've
> > > > queued the patch.
> > > Please don't.
> > >
> > > These programs are examples to help people understand how the
> > > ivhsmem
> > > device works. They might even be useful for debugging. They are
> > > *not*
> > > to be used in production.
> >
> > Oooookay. :) It needs to be documented in the changelog.
>
> I'll take care of updating <https://wiki.qemu.org/ChangeLog/5.2>;.
>
Thanks all for the clarification on this one. It was packaged up simply
because it got installed, and I never got to looking at the use case
for these binaries.
I'll remove them from what we package in SUSE's SLE and openSUSE.
- Bruce
next prev parent reply other threads:[~2020-09-04 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 15:35 [PATCH] meson: install ivshmem-client and ivshmem-server Bruce Rogers
2020-09-03 15:42 ` Marc-André Lureau
2020-09-03 15:44 ` Paolo Bonzini
2020-09-03 15:49 ` Daniel P. Berrangé
2020-09-03 16:10 ` Bruce Rogers
2020-09-03 17:55 ` Paolo Bonzini
2020-09-04 7:24 ` Markus Armbruster
2020-09-04 7:57 ` Paolo Bonzini
2020-09-04 9:20 ` Markus Armbruster
2020-09-04 11:49 ` Bruce Rogers [this message]
2020-09-04 13:39 ` Markus Armbruster
2020-09-04 9:37 ` Philippe Mathieu-Daudé
2020-09-04 10:27 ` Daniel P. Berrangé
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=5636584a23452c45d91f535e77374c37aaadcb48.camel@suse.com \
--to=brogers@suse.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).