From: "João Peixoto" <jpeixoto@osyx.tech>
To: Andrew Jones <andrew.jones@oss.qualcomm.com>, joaopeixoto@osyx.tech
Cc: linux-kernel@vger.kernel.org, ajd@linux.ibm.com, alex@ghiti.fr,
aou@eecs.berkeley.edu, bagasdotme@gmail.com,
catalin.marinas@arm.com, conor+dt@kernel.org, corbet@lwn.net,
dan.j.williams@intel.com, davidmcerdeira@osyx.tech,
devicetree@vger.kernel.org, dev@kael-k.io,
gregkh@linuxfoundation.org, haren@linux.ibm.com, heiko@sntech.de,
jose@osyx.tech, kever.yang@rock-chips.com, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-riscv@lists.infradead.org, maddy@linux.ibm.com,
mani@kernel.org, nathan@kernel.org, neil.armstrong@linaro.org,
palmer@dabbelt.com, pjw@kernel.org,
prabhakar.mahadev-lad.rj@bp.renesas.com, robh@kernel.org,
will@kernel.org
Subject: Re: [PATCH 5/6] virt: bao: Move BAO_IPCSHMEM_HYPERCALL_ID to common header
Date: Fri, 7 Aug 2026 08:44:29 +0100 [thread overview]
Message-ID: <96442d4d-ec8c-4637-89a2-9dcbca7bb98b@osyx.tech> (raw)
In-Reply-To: <5kjiicdwq2ny3zg4mooojsntylukuadx4ajhf7mn7sue4aedpk@j2xfslwvkwur>
On 1/14/26 20:34, Andrew Jones wrote:
> On Wed, Jan 07, 2026 at 04:28:28PM +0000,joaopeixoto@osyx.tech wrote:
>> From: João Peixoto<joaopeixoto@osyx.tech>
>>
>> Move the IPC shared-memory hypercall ID from architecture-specific
>> headers into include/linux/bao.h.
> The series should be rebased to have this fixup integrated into the
> previous patches where the code is first introduced.
>
> Thanks,
> drew
Understood. The reason it is currently a separate patch is layering: the
shared header include/linux/bao.h is introduced by the I/O dispatcher patch
(4/6), while the IPC helper that would use the constant is introduced
earlier
(2/6). To fold this away cleanly I will move creation of include/linux/bao.h
into 2/6 (with the IPC hypercall ID) and have 4/6 only add the Remote
I/O ID,
so the arch helpers are parameter-free from the start and this patch
disappears. I will do that in v4 (I kept it separate in v3 only so the
changelog against v2 stays readable, and it now has a proper "why" message).
If you would prefer I fold it immediately, I am happy to respin.
next prev parent reply other threads:[~2026-08-07 7:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 13:52 [PATCH 0/5] virt: Add Bao hypervisor IPC and I/O dispatcher drivers joaopeixoto
2025-12-24 13:52 ` [PATCH 1/5] dt-bindings: Add Bao IPC shared memory driver binding joaopeixoto
2025-12-24 16:18 ` Rob Herring (Arm)
2025-12-25 8:57 ` Krzysztof Kozlowski
2025-12-24 13:52 ` [PATCH 2/5] virt: add Bao IPC shared memory driver joaopeixoto
2025-12-24 15:53 ` Greg KH
2025-12-24 15:54 ` Greg KH
2025-12-25 9:02 ` Krzysztof Kozlowski
2025-12-24 13:52 ` [PATCH 3/5] dt-bindings: Add Bao I/O dispatcher driver binding joaopeixoto
2025-12-24 16:18 ` Rob Herring (Arm)
2025-12-25 8:58 ` Krzysztof Kozlowski
2025-12-24 13:52 ` [PATCH 4/5] virt: add Bao I/O dispatcher driver joaopeixoto
2025-12-25 9:12 ` Krzysztof Kozlowski
2025-12-24 13:52 ` [PATCH 5/5] MAINTAINERS: Add entries for Bao hypervisor drivers, headers, and DT bindings joaopeixoto
2025-12-25 8:52 ` Krzysztof Kozlowski
2025-12-25 8:51 ` [PATCH 0/5] virt: Add Bao hypervisor IPC and I/O dispatcher drivers Krzysztof Kozlowski
2026-01-07 16:28 ` [PATCH v2 0/6] " joaopeixoto
2026-01-07 16:28 ` [PATCH 1/6] dt-bindings: Add Bao IPC shared memory driver binding joaopeixoto
2026-01-07 16:46 ` Krzysztof Kozlowski
2026-08-07 7:41 ` João Peixoto
2026-08-07 7:50 ` Krzysztof Kozlowski
2026-01-07 16:28 ` [PATCH 2/6] virt: bao: Add Bao IPC shared memory driver joaopeixoto
2026-01-07 18:54 ` Randy Dunlap
2026-08-07 7:42 ` João Peixoto
2026-01-14 20:37 ` Andrew Jones
2026-08-07 7:42 ` João Peixoto
2026-01-07 16:28 ` [PATCH 3/6] dt-bindings: Add Bao I/O dispatcher driver binding joaopeixoto
2026-01-07 16:47 ` Krzysztof Kozlowski
2026-08-07 7:43 ` João Peixoto
2026-08-07 7:51 ` Krzysztof Kozlowski
2026-01-07 16:28 ` [PATCH 4/6] virt: bao: Add Bao I/O dispatcher driver joaopeixoto
2026-01-14 20:32 ` Andrew Jones
2026-08-07 7:43 ` João Peixoto
2026-01-07 16:28 ` [PATCH 5/6] virt: bao: Move BAO_IPCSHMEM_HYPERCALL_ID to common header joaopeixoto
2026-01-07 19:36 ` Greg KH
2026-08-07 7:43 ` João Peixoto
2026-01-14 20:34 ` Andrew Jones
2026-08-07 7:44 ` João Peixoto [this message]
2026-01-07 16:28 ` [PATCH 6/6] MAINTAINERS: Add entries for Bao hypervisor drivers, headers, and DT bindings joaopeixoto
2026-01-07 19:37 ` [PATCH v2 0/6] virt: Add Bao hypervisor IPC and I/O dispatcher drivers Greg KH
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=96442d4d-ec8c-4637-89a2-9dcbca7bb98b@osyx.tech \
--to=jpeixoto@osyx.tech \
--cc=ajd@linux.ibm.com \
--cc=alex@ghiti.fr \
--cc=andrew.jones@oss.qualcomm.com \
--cc=aou@eecs.berkeley.edu \
--cc=bagasdotme@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=davidmcerdeira@osyx.tech \
--cc=dev@kael-k.io \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=haren@linux.ibm.com \
--cc=heiko@sntech.de \
--cc=joaopeixoto@osyx.tech \
--cc=jose@osyx.tech \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maddy@linux.ibm.com \
--cc=mani@kernel.org \
--cc=nathan@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=will@kernel.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