Linux Serial subsystem development
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"kernel test robot" <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-serial@vger.kernel.org,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Javier Martinez Canillas" <javierm@redhat.com>
Subject: Re: [tty:tty-testing 22/24] earlycon.c:undefined reference to `screen_info'
Date: Tue, 17 Oct 2023 10:25:41 +0200	[thread overview]
Message-ID: <a2a975ee-9398-45ba-859e-69212a076525@app.fastmail.com> (raw)
In-Reply-To: <2023101722-outage-outward-a6d6@gregkh>

On Tue, Oct 17, 2023, at 10:18, Greg Kroah-Hartman wrote:
> On Tue, Oct 17, 2023 at 09:44:58AM +0800, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
>> head:   6271f1e8c4cb9a46273ae01ff9cb86a022063f75
>> commit: 934d62223da320b3ec012c85b63a6c250f507096 [22/24] efi: move screen_info into efi init code
>> config: loongarch-randconfig-002-20231017 (https://download.01.org/0day-ci/archive/20231017/202310170938.xHIu2lFB-lkp@intel.com/config)
>> compiler: loongarch64-linux-gcc (GCC) 13.2.0
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231017/202310170938.xHIu2lFB-lkp@intel.com/reproduce)
>> 
>> If you fix the issue in a separate patch/commit (i.e. not just a new version of
>> the same patch/commit), kindly add following tags
>> | Reported-by: kernel test robot <lkp@intel.com>
>> | Closes: https://lore.kernel.org/oe-kbuild-all/202310170938.xHIu2lFB-lkp@intel.com/
>
> Arnd, I'll drop this commit from my tree now, if you want to fix it up
> and resend just it, I'll be glad to apply it.

Ok, I was about to send the fixup below, but I'll just send the
combined patch instead then. I'm still looking at another build
regression from the same series that I'll fix up as well.

    Arnd

----
From 8f8bebf0be1e61fdb38f73e71f05066caebf64e4 Mon Sep 17 00:00:00 2001
From: Arnd Bergmann <arnd@arndb.de>
Date: Tue, 17 Oct 2023 08:11:35 +0200
Subject: [PATCH] efi: move screen_info for loongarch as well

I had intended to move the screen_info definition next to the global
init_screen_info() function that is shared between all architectures,
but as it turns out, loongarch does not actually use this file and
instead has its own copy and is now missing the structure:

   loongarch64-linux-ld: arch/loongarch/kernel/efi.o: in function `efi_init':
   efi.c:(.init.text+0x158): undefined reference to `screen_info'

Add another copy next to the loongarch specific function, the same
way that x86 already has a special case for this.

Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202310171049.aNxOKhUY-lkp@intel.com/
Closes: https://lore.kernel.org/oe-kbuild-all/202310170938.xHIu2lFB-lkp@intel.com/
Fixes: 934d62223da320 ("efi: move screen_info into efi init code")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>

diff --git a/arch/loongarch/kernel/efi.c b/arch/loongarch/kernel/efi.c
index df7db34024e61..acb5d3385675c 100644
--- a/arch/loongarch/kernel/efi.c
+++ b/arch/loongarch/kernel/efi.c
@@ -68,6 +68,11 @@ void __init efi_runtime_init(void)
 
 unsigned long __initdata screen_info_table = EFI_INVALID_TABLE_ADDR;
 
+#if defined(CONFIG_SYSFB) || defined(CONFIG_EFI_EARLYCON)
+struct screen_info screen_info __section(".data");
+EXPORT_SYMBOL_GPL(screen_info);
+#endif
+
 static void __init init_screen_info(void)
 {
 	struct screen_info *si;



      reply	other threads:[~2023-10-17  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  1:44 [tty:tty-testing 22/24] earlycon.c:undefined reference to `screen_info' kernel test robot
2023-10-17  8:18 ` Greg Kroah-Hartman
2023-10-17  8:25   ` Arnd Bergmann [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=a2a975ee-9398-45ba-859e-69212a076525@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=ardb@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=javierm@redhat.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox