From: John Levon <john.levon@nutanix.com>
To: "Carlos López" <clopez@suse.de>
Cc: qemu-devel@nongnu.org,
"Thanos Makatos" <thanos.makatos@nutanix.com>,
"Cédric Le Goater" <clg@redhat.com>
Subject: Re: [PATCH] docs/system: fix vfio-user console example format
Date: Tue, 21 Oct 2025 12:05:21 +0200 [thread overview]
Message-ID: <aPda4Ri6qHXWA3sj@lent> (raw)
In-Reply-To: <20251021093550.766872-2-clopez@suse.de>
On Tue, Oct 21, 2025 at 11:35:51AM +0200, Carlos López wrote:
> The rendering for the console example for vfio-user is displayed
> incorrectly because of a missing indentation, causing the example to be
> shown as regular text. Fix this by adding the required indentation.
Thanks but this is a duplicate of:
https://lore.kernel.org/qemu-devel/20251009140206.386249-1-john.levon@nutanix.com/
regards
john
next prev parent reply other threads:[~2025-10-21 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 9:35 [PATCH] docs/system: fix vfio-user console example format Carlos López
2025-10-21 10:05 ` John Levon [this message]
2025-10-21 10:06 ` Cédric Le Goater
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=aPda4Ri6qHXWA3sj@lent \
--to=john.levon@nutanix.com \
--cc=clg@redhat.com \
--cc=clopez@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=thanos.makatos@nutanix.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).