From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, mst@redhat.com, t0rr3sp3dr0@gmail.com,
alex.bennee@linaro.org, dgilbert@redhat.com, agraf@suse.de
Subject: Re: [PATCH for-7.1] applesmc: silence invalid key warning in case default one is used
Date: Thu, 28 Jul 2022 14:42:52 +0100 [thread overview]
Message-ID: <YuKSXDgCmmBNJndy@redhat.com> (raw)
In-Reply-To: <CAFEAcA_GfY8uDA+z8NSOebw1MKoaNoCNYiRBss3Ku-Q-jTBeWg@mail.gmail.com>
On Thu, Jul 28, 2022 at 02:40:22PM +0100, Peter Maydell wrote:
> On Thu, 28 Jul 2022 at 14:30, Markus Armbruster <armbru@redhat.com> wrote:
> > Peter Maydell <peter.maydell@linaro.org> writes:
> > I applaud the renaissance of roman-style inscriptions, but it's not just
> > words without spaces, it's also capital letters only:
> >
> > ANY64CHARACTERFAKEOSKISENOUGHTOPREVENTINVALIDKEYWARNINGSONSTDERR
> >
> > Seriously, throw in some dashes or spaces.
>
> any-64-char-fake-osk-will-avoid-an-invalid-key-warning-on-stderr
On the basis that virtualization gives you turtles all the way down...
-device isa-applesmc,osk=🐢🐢🐢🐢🐢🐢🐢🐢🐢🐢🐢🐢🐢🐢🐢🐢
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-07-28 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 9:35 [PATCH for-7.1] applesmc: silence invalid key warning in case default one is used Igor Mammedov
2022-07-28 9:48 ` Daniel P. Berrangé
2022-07-28 10:05 ` Peter Maydell
2022-07-28 10:23 ` Daniel P. Berrangé
2022-07-28 10:52 ` Peter Maydell
2022-07-28 13:29 ` Markus Armbruster
2022-07-28 13:39 ` Igor Mammedov
2022-07-28 13:40 ` Peter Maydell
2022-07-28 13:42 ` Daniel P. Berrangé [this message]
2022-07-28 14:51 ` Markus Armbruster
2022-07-28 12:00 ` Igor Mammedov
2022-07-28 12:59 ` Daniel P. Berrangé
2022-07-28 12:08 ` Igor Mammedov
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=YuKSXDgCmmBNJndy@redhat.com \
--to=berrange@redhat.com \
--cc=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=t0rr3sp3dr0@gmail.com \
/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).