From: Jan Beulich <jbeulich@suse.com>
To: Sergiy Kibrik <Sergiy_Kibrik@epam.com>
Cc: Nicola Vetrini <nicola.vetrini@bugseng.com>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 3/4] automation: rename CONFIG_MEM_ACCESS -> CONFIG_VM_EVENT
Date: Thu, 30 Jan 2025 14:14:58 +0100 [thread overview]
Message-ID: <99b26eb1-eed7-4eb0-8be5-d1e971eede8a@suse.com> (raw)
In-Reply-To: <e43444e0cd04bf08edf47ee4c56d0aa675d19534.1737452864.git.Sergiy_Kibrik@epam.com>
On 21.01.2025 11:23, Sergiy Kibrik wrote:
> Following the renaming of Xen build option.
>
> Signed-off-by: Sergiy Kibrik <Sergiy_Kibrik@epam.com>
> ---
> automation/eclair_analysis/xen_arm_config | 2 +-
> automation/eclair_analysis/xen_x86_config | 2 +-
> automation/gitlab-ci/build.yaml | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
This can't really be separated from the changes doing the actual rename,
can it? Aiui the build (randconfig ones in particular) may break between
the two patches, or what is being tested may end up being different.
Jan
next prev parent reply other threads:[~2025-01-30 13:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 10:17 [PATCH v2 0/4] make build of vm_event/mem_access/monitor optional Sergiy Kibrik
2025-01-21 10:19 ` [PATCH v2 1/4] xen: kconfig: rename MEM_ACCESS -> VM_EVENT Sergiy Kibrik
2025-01-30 13:24 ` Jan Beulich
2025-01-31 0:26 ` Tamas K Lengyel
2025-01-31 6:30 ` Jan Beulich
2025-01-31 23:36 ` Tamas K Lengyel
2025-02-03 7:36 ` Jan Beulich
2025-02-04 1:07 ` Tamas K Lengyel
2025-01-30 13:26 ` Jan Beulich
2025-01-31 0:29 ` Tamas K Lengyel
2025-01-21 10:21 ` [PATCH v2 2/4] x86:monitor: control monitor.c build with CONFIG_VM_EVENT option Sergiy Kibrik
2025-01-30 13:27 ` Jan Beulich
2025-01-21 10:23 ` [PATCH v2 3/4] automation: rename CONFIG_MEM_ACCESS -> CONFIG_VM_EVENT Sergiy Kibrik
2025-01-22 8:03 ` Nicola Vetrini
2025-01-30 13:14 ` Jan Beulich [this message]
2025-01-21 10:25 ` [PATCH v2 4/4] xen: mem_access: conditionally compile vm_event.c & monitor.c Sergiy Kibrik
2025-01-30 13:32 ` Jan Beulich
2025-01-31 0:33 ` Tamas K Lengyel
2025-01-31 6:42 ` 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=99b26eb1-eed7-4eb0-8be5-d1e971eede8a@suse.com \
--to=jbeulich@suse.com \
--cc=Sergiy_Kibrik@epam.com \
--cc=cardoe@cardoe.com \
--cc=nicola.vetrini@bugseng.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.