All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH joro] x86/head/64: startup_gdt[] can be static
Date: Sat, 18 Jul 2020 10:07:52 +0800	[thread overview]
Message-ID: <20200718020752.GA13077@48b94b458c98> (raw)
In-Reply-To: <202007181014.Nc7hu4Gg%lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]


Fixes: c12cc81e6b52 ("x86/head/64: Install startup GDT")
Signed-off-by: kernel test robot <lkp@intel.com>
---
 head64.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kernel/head64.c b/arch/x86/kernel/head64.c
index 74766728baf32..0f12adcc3bf83 100644
--- a/arch/x86/kernel/head64.c
+++ b/arch/x86/kernel/head64.c
@@ -64,7 +64,7 @@ EXPORT_SYMBOL(vmemmap_base);
 /*
  * GDT used on the boot CPU before switching to virtual addresses.
  */
-struct desc_struct startup_gdt[GDT_ENTRIES] = {
+static struct desc_struct startup_gdt[GDT_ENTRIES] = {
 	[GDT_ENTRY_KERNEL32_CS]         = GDT_ENTRY_INIT(0xc09b, 0, 0xfffff),
 	[GDT_ENTRY_KERNEL_CS]           = GDT_ENTRY_INIT(0xa09b, 0, 0xfffff),
 	[GDT_ENTRY_KERNEL_DS]           = GDT_ENTRY_INIT(0xc093, 0, 0xfffff),
@@ -74,7 +74,7 @@ struct desc_struct startup_gdt[GDT_ENTRIES] = {
  * Address needs to be set at runtime because it references the startup_gdt while
  * the kernel still uses a direct mapping.
  */
-struct desc_ptr startup_gdt_descr = {
+static struct desc_ptr startup_gdt_descr = {
 	.size = sizeof(startup_gdt),
 	.address = 0,
 };

      reply	other threads:[~2020-07-18  2:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18  2:07 [joro:sev-es-client-tip 29/76] arch/x86/kernel/head64.c:67:20: sparse: sparse: symbol 'startup_gdt' was not declared. Should it be kernel test robot
2020-07-18  2:07 ` kernel test robot [this message]

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=20200718020752.GA13077@48b94b458c98 \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.