From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Gustavo Romero <gustavo.romero@linaro.org>,
qemu-devel@nongnu.org, alex.bennee@linaro.org
Subject: Re: [PATCH v2 0/2] Add me as the maintainer for ivshmem-pci
Date: Sat, 01 Feb 2025 08:08:38 +0100 [thread overview]
Message-ID: <87seoyjg5l.fsf@pond.sub.org> (raw)
In-Reply-To: <f16985e1-ecc5-4439-ba4c-f9a6a4d06d10@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Fri, 31 Jan 2025 19:33:59 +0100")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> On 24/1/25 17:22, Philippe Mathieu-Daudé wrote:
>> On 23/1/25 02:22, Gustavo Romero wrote:
>>> Add me as the maintainer for the ivshmem-pci.c device, the ivshmem
>>> server, and the ivshmem client tool. Also, adjust remaining parts left
>>> behind after ivshmem PCI device was renamed from ivshmem.c to
>>> ivshmem-pci.c, like header files, Kconfig, docs, and build scripts.
>>>
>>>
>>> Cheers,
>>> Gustavo
>>>
>>> Gustavo Romero (2):
>>> hw/misc/ivshmem-pci: Rename remaining parts for consistency
>>> MAINTAINERS: Add me as the maintainer for ivshmem-pci
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> and queued, thanks for volunteering!
>
> Failing to build:
>
> docs/specs/ivshmem-spec.rst:17:unknown document: '../system/devices/ivshmem'
> ninja: build stopped: subcommand failed.
>
> docs/specs/ivshmem-spec.rst only mention PCI, so I could squash in the
> first patch:
> -- >8 --
> diff --git a/docs/specs/ivshmem-spec.rst b/docs/specs/ivshmem-spec.rst
> index 2d8e80055b0..e326d024487 100644
> --- a/docs/specs/ivshmem-spec.rst
> +++ b/docs/specs/ivshmem-spec.rst
> @@ -17,3 +17,3 @@ get interrupted by its peers.
> For information on configuring the ivshmem device on the QEMU
> -command line, see :doc:`../system/devices/ivshmem`.
> +command line, see :doc:`../system/devices/ivshmem-pci`.
> ---
> But then I wonder if this document shouldn't mention the flat
> device. Since I'm unsure I'm dropping the series (patch 2
> depends on 1).
Simple oversight in PATCH 1. It renames docs/system/devices/ivshmem.rst
to docs/system/devices/ivshmem-pci.rst without updating the reference in
docs/specs/ivshmem-spec.rst.
Surprisingly, this didn't fail for me in an incremental build, only in a
full one.
prev parent reply other threads:[~2025-02-01 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 1:22 [PATCH v2 0/2] Add me as the maintainer for ivshmem-pci Gustavo Romero
2025-01-23 1:22 ` [PATCH v2 1/2] hw/misc/ivshmem-pci: Rename remaining parts for consistency Gustavo Romero
2025-01-23 1:22 ` [PATCH v2 2/2] MAINTAINERS: Add me as the maintainer for ivshmem-pci Gustavo Romero
2025-01-24 7:29 ` [PATCH v2 0/2] " Markus Armbruster
2025-01-24 16:22 ` Philippe Mathieu-Daudé
2025-01-31 18:33 ` Philippe Mathieu-Daudé
2025-02-01 7:08 ` Markus Armbruster [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=87seoyjg5l.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=gustavo.romero@linaro.org \
--cc=philmd@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.