qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Sean Wei <me@sean.taipei>, qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Ani Sinha <anisinha@redhat.com>,
	Gustavo Romero <gustavo.romero@linaro.org>,
	Nicholas Piggin <npiggin@gmail.com>,
	Daniel Henrique Barboza <danielhb413@gmail.com>,
	Harsh Prateek Bora <harshpb@linux.ibm.com>,
	Fabiano Rosas <farosas@suse.de>,
	Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"open list:sPAPR (pseries)" <qemu-ppc@nongnu.org>
Subject: Re: [PATCH 5/6] treewide: update docs file extensions (.txt -> .rst) in comments
Date: Tue, 1 Jul 2025 19:28:21 +0200	[thread overview]
Message-ID: <d96479ff-a239-421f-a697-b19dc4a8fa1e@redhat.com> (raw)
In-Reply-To: <20250616.qemu.relocated.05@sean.taipei>

On 16/06/2025 17.50, Sean Wei wrote:
> Several source comments still refer to docs with the old .txt
> extension that were previously converted to reStructuredText.
> 
> Update these references to use the correct .rst extensions to
> maintain accurate in-tree documentation pointers.
> 
> No functional changes.
> 
> Related commits:
>    50f8174c5c1 (Jul 2021): docs/specs/acpi_nvdimm: Convert to rST
>    f054eb1c920 (Jul 2021): docs/specs/acpi_pci_hotplug: Convert to rST
>    912fb3678b8 (Sep 2023): docs/specs/vmgenid: Convert to rST
>    bb1cff6ee04 (Sep 2023): docs/specs/ivshmem-spec: Convert to rST
>    55ff468f781 (Jan 2022): docs: Rename ppc-spapr-hotplug.txt to .rst
> 
> Signed-off-by: Sean Wei <me@sean.taipei>
> ---
>   hw/acpi/nvdimm.c               | 2 +-
>   hw/acpi/pcihp.c                | 2 +-
>   hw/acpi/vmgenid.c              | 6 +++---
>   hw/misc/ivshmem-flat.c         | 2 +-
>   hw/ppc/spapr.c                 | 2 +-
>   include/hw/acpi/pcihp.h        | 2 +-
>   include/hw/misc/ivshmem-flat.h | 2 +-
>   tests/qtest/vmgenid-test.c     | 2 +-
>   8 files changed, 10 insertions(+), 10 deletions(-)

Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2025-07-01 17:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 15:46 [PATCH 0/6] Fix paths for relocated files Sean Wei
2025-06-16 15:47 ` [PATCH 1/6] MAINTAINERS: update docs file extensions (.txt -> .rst) Sean Wei
2025-07-01 17:18   ` Thomas Huth
2025-06-16 15:48 ` [PATCH 2/6] MAINTAINERS: fix paths for relocated files Sean Wei
2025-07-01 17:24   ` Thomas Huth
2025-07-01 18:06     ` Sean Wei
2025-07-01 18:54       ` Thomas Huth
2025-06-16 15:49 ` [PATCH 3/6] MAINTAINERS: fix vendor capitalization (Vmware -> VMware) Sean Wei
2025-06-16 15:50 ` [PATCH 4/6] MAINTAINERS: fix VMware filename typo (vwm -> vmw) Sean Wei
2025-07-01 17:25   ` Thomas Huth
2025-06-16 15:50 ` [PATCH 5/6] treewide: update docs file extensions (.txt -> .rst) in comments Sean Wei
2025-07-01 17:28   ` Thomas Huth [this message]
2025-07-02  5:50   ` Harsh Prateek Bora
2025-06-16 15:51 ` [PATCH 6/6] treewide: fix paths for relocated files " Sean Wei
2025-07-01 17:32   ` Thomas Huth

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=d96479ff-a239-421f-a697-b19dc4a8fa1e@redhat.com \
    --to=thuth@redhat.com \
    --cc=anisinha@redhat.com \
    --cc=danielhb413@gmail.com \
    --cc=farosas@suse.de \
    --cc=gustavo.romero@linaro.org \
    --cc=harshpb@linux.ibm.com \
    --cc=imammedo@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=me@sean.taipei \
    --cc=mst@redhat.com \
    --cc=npiggin@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).