From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Shawn Anastasio <sanastasio@raptorengineering.com>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>,
George Dunlap <George.Dunlap@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 3/3] xen/ppc: Avoid using the legacy __read_mostly/__ro_after_init definitions
Date: Mon, 24 Jun 2024 10:01:20 +0200 [thread overview]
Message-ID: <71f97e26-cbb5-4e6b-860a-8c3de1e7e8df@suse.com> (raw)
In-Reply-To: <20240621201928.319293-4-andrew.cooper3@citrix.com>
On 21.06.2024 22:19, Andrew Cooper wrote:
> RISC-V wants to introduce a full build of Xen without using the legacy
> definitions. PPC64 has the most minimal full build of Xen right now, so make
> it compile without the legacy definitions.
>
> Mostly this is just including xen/sections.h in a variety of common files. In
> a couple of cases, we can drop an inclusion of {xen,asm}/cache.h, but almost
> all files get the definitions transitively.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2024-06-24 8:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 20:19 [PATCH for-4.19? 0/3] xen: build adjustments for __read_mostly/__ro_after_init Andrew Cooper
2024-06-21 20:19 ` [PATCH 1/3] xen/riscv: Drop legacy __ro_after_init definition Andrew Cooper
2024-06-24 8:02 ` Oleksii
2024-06-24 8:04 ` Jan Beulich
2024-06-24 12:51 ` Oleksii
2024-06-24 12:50 ` Oleksii
2024-06-21 20:19 ` [PATCH 2/3] xen/ppc: Adjust ppc64_defconfig Andrew Cooper
2024-09-05 21:54 ` [ping] " Andrew Cooper
2024-09-06 6:01 ` Jan Beulich
2024-06-21 20:19 ` [PATCH 3/3] xen/ppc: Avoid using the legacy __read_mostly/__ro_after_init definitions Andrew Cooper
2024-06-24 8:01 ` Jan Beulich [this message]
2024-06-24 8:04 ` Oleksii
2024-06-24 7:58 ` [PATCH for-4.19? 0/3] xen: build adjustments for __read_mostly/__ro_after_init Oleksii
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=71f97e26-cbb5-4e6b-860a-8c3de1e7e8df@suse.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien@xen.org \
--cc=oleksii.kurochko@gmail.com \
--cc=sanastasio@raptorengineering.com \
--cc=sstabellini@kernel.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.