From: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Doug Goldstein" <cardoe@cardoe.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 0/4] Add Kconfig option to remove microcode loading support
Date: Tue, 20 Jan 2026 11:38:55 +0100 [thread overview]
Message-ID: <DFTCOGP65Q9O.3S2TVE18USSUP@amd.com> (raw)
In-Reply-To: <d5620135-5e91-4223-a0ba-c6876fb8702f@suse.com>
On Tue Jan 20, 2026 at 11:20 AM CET, Jan Beulich wrote:
> On 20.01.2026 10:38, Alejandro Vallejo wrote:
>> The only dependency here is patch 2 going in before patch 3. Everything else
>> can be freely rearranged.
>
> Is this correct? Didn't you say (confirming what I observed elsewhere a little
> while back) that there's a complaint when a file listed in the exclusions doesn't
> exist anymore (which may have been cppcheck, not Eclair, but still breaking CI)?
> IOW can patch 4 really be separate from patch 3? Or, if its description was to
> be trusted, wouldn't it need to go ahead of what is now patch 3?
Doh, you're right, they are out of order. Patch 4 now just removes the exclusion
so it's fine to do it separately.
So patch3 <-> patch4.
Cheers,
Alejandro
next prev parent reply other threads:[~2026-01-20 10:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 9:38 [PATCH v4 0/4] Add Kconfig option to remove microcode loading support Alejandro Vallejo
2026-01-20 9:38 ` [PATCH v4 1/5] x86/ucode: Add Kconfig option to remove microcode loading Alejandro Vallejo
2026-01-20 14:09 ` Andrew Cooper
2026-01-20 15:29 ` Alejandro Vallejo
2026-01-20 9:38 ` [PATCH v4 2/5] xen: Allow lib-y targets to also be .init.o Alejandro Vallejo
2026-01-20 10:23 ` Jan Beulich
2026-01-20 9:38 ` [PATCH v4 3/5] earlycpio: lib-ify earlycpio.c Alejandro Vallejo
2026-01-20 14:07 ` Andrew Cooper
2026-01-20 9:38 ` [PATCH v4 4/5] docs/misra: Remove earlycpio.c from the Eclair exclusion list Alejandro Vallejo
2026-01-20 11:21 ` Nicola Vetrini
2026-01-20 11:27 ` Alejandro Vallejo
2026-01-20 11:41 ` Nicola Vetrini
2026-01-20 11:51 ` Alejandro Vallejo
2026-01-20 12:02 ` Nicola Vetrini
2026-01-20 12:09 ` Alejandro Vallejo
2026-01-20 14:20 ` Nicola Vetrini
2026-01-20 15:14 ` Andrew Cooper
2026-01-20 15:25 ` Nicola Vetrini
2026-01-20 17:31 ` Andrew Cooper
2026-01-20 9:38 ` [PATCH v4 5/5] automation: Disable ucode loading on AMD's analysis run Alejandro Vallejo
2026-01-20 10:53 ` Alejandro Vallejo
2026-01-21 10:44 ` Andrew Cooper
2026-01-21 19:55 ` Stefano Stabellini
2026-01-20 10:20 ` [PATCH v4 0/4] Add Kconfig option to remove microcode loading support Jan Beulich
2026-01-20 10:38 ` Alejandro Vallejo [this message]
2026-01-20 10:52 ` Jan Beulich
2026-01-20 11:03 ` Alejandro Vallejo
2026-01-20 11:30 ` Nicola Vetrini
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=DFTCOGP65Q9O.3S2TVE18USSUP@amd.com \
--to=alejandro.garciavallejo@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=cardoe@cardoe.com \
--cc=dpsmith@apertussolutions.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=marmarek@invisiblethingslab.com \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.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.