From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
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:18:46 +0200 [thread overview]
Message-ID: <2023101722-outage-outward-a6d6@gregkh> (raw)
In-Reply-To: <202310170938.xHIu2lFB-lkp@intel.com>
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.
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-17 8:18 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 [this message]
2023-10-17 8:25 ` Arnd Bergmann
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=2023101722-outage-outward-a6d6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--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