From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH 2/n] x86/microcode: Move interface from processor.h to microcode.h
Date: Thu, 19 Mar 2020 10:22:44 +0100 [thread overview]
Message-ID: <33d4211d-aa87-dbd9-32f6-09845079f545@suse.com> (raw)
In-Reply-To: <20200318213057.19214-1-andrew.cooper3@citrix.com>
On 18.03.2020 22:30, Andrew Cooper wrote:
> This reduces the complexity of processor.h, particularly the need to include
> public/xen.h. Substitute processor.h includes for microcode.h in some
> sources, and add microcode.h includes in others.
>
> Only 4 of the 7 function declarations are actually called externally.
> early_microcode_update_cpu() has no callers so make it static, and move the
> vendor init declarations to private.h
>
> No functional change.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-03-19 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 21:05 [Xen-devel] [PATCH] xen/x86: Move microcode into its own directory Andrew Cooper
2020-03-18 21:30 ` [Xen-devel] [PATCH 2/n] x86/microcode: Move interface from processor.h to microcode.h Andrew Cooper
2020-03-19 9:22 ` Jan Beulich [this message]
2020-03-18 21:42 ` [Xen-devel] [PATCH] xen/x86: Move microcode into its own directory Andrew Cooper
2020-03-19 9:21 ` Jan Beulich
2020-03-19 9:21 ` Jan Beulich
2020-03-19 9:52 ` Andrew Cooper
2020-03-19 9:59 ` Jan Beulich
2020-03-19 10:41 ` Andrew Cooper
2020-03-19 11:16 ` 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=33d4211d-aa87-dbd9-32f6-09845079f545@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.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.