From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: Tamas K Lengyel <tamas.k.lengyel@gmail.com>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: [PATCH v1 0/2] introduce stub directory to storing empty/stub headers
Date: Mon, 28 Aug 2023 18:57:06 +0300 [thread overview]
Message-ID: <cover.1693235841.git.oleksii.kurochko@gmail.com> (raw)
A lot of empty/stub headers should be introduced during the early steps of adding
support of new architecture.
An example can be found here:
1. https://lore.kernel.org/xen-devel/cover.1692181079.git.oleksii.kurochko@gmail.com/
2. https://lore.kernel.org/xen-devel/a92f99e8f697da99d77bfde562a549dbef3760ce.1692816595.git.sanastasio@raptorengineering.com/
As part of the patch series, asm/vm_event.h was moved to the stubs directory because
It is the same for ARM, PPC, and RISC-V.
Oleksii Kurochko (2):
xen: add stubs dir to include path
xen: move arm/include/asm/vm_event.h to stubs
xen/Makefile | 1 +
xen/arch/arm/include/asm/vm_event.h | 66 -----------------------------
xen/include/stubs/asm/vm_event.h | 55 ++++++++++++++++++++++++
3 files changed, 56 insertions(+), 66 deletions(-)
delete mode 100644 xen/arch/arm/include/asm/vm_event.h
create mode 100644 xen/include/stubs/asm/vm_event.h
--
2.41.0
next reply other threads:[~2023-08-28 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 15:57 Oleksii Kurochko [this message]
2023-08-28 15:57 ` [PATCH v1 1/2] xen: add stubs dir to include path Oleksii Kurochko
2023-08-28 15:57 ` [PATCH v1 2/2] xen: move arm/include/asm/vm_event.h to stubs Oleksii Kurochko
2023-08-28 16:05 ` Jan Beulich
2023-08-29 12:14 ` Oleksii
2023-08-29 12:19 ` Jan Beulich
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=cover.1693235841.git.oleksii.kurochko@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=tamas.k.lengyel@gmail.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.