From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>,
Youling Tang <tangyouling@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
oe-kbuild-all@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Sean Christopherson <seanjc@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v1 1/1] serial: 8250_platform: Explicitly show we initialise ISA ports only once
Date: Tue, 11 Jun 2024 18:55:16 +0300 [thread overview]
Message-ID: <ZmhzZJdK9IgBYauE@smile.fi.intel.com> (raw)
In-Reply-To: <202406072102.SGp8FYYi-lkp@intel.com>
+Cc: initial authors of Loongarch64 jump table implementation and people who touched that code.
On Fri, Jun 07, 2024 at 09:48:51PM +0800, kernel test robot wrote:
> Hi Andy,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on tty/tty-testing]
> [also build test WARNING on tty/tty-next next-20240607]
> [cannot apply to tty/tty-linus linus/master v6.10-rc2]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Andy-Shevchenko/serial-8250_platform-Explicitly-show-we-initialise-ISA-ports-only-once/20240607-025109
> base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
> patch link: https://lore.kernel.org/r/20240606184841.3102545-1-andriy.shevchenko%40linux.intel.com
> patch subject: [PATCH v1 1/1] serial: 8250_platform: Explicitly show we initialise ISA ports only once
> config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20240607/202406072102.SGp8FYYi-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/20240607/202406072102.SGp8FYYi-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/202406072102.SGp8FYYi-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> drivers/tty/serial/8250/8250_platform.o: warning: objtool: __jump_table+0x0: special: can't find orig instruction
>
> objdump-func vmlinux.o __jump_table:
Folks, can you look into it? It sounds like jump table is misimplemented for
this architecture (but I'm quite unsure). Similar issue LKP reported here:
https://lore.kernel.org/all/202405290629.oaN9XxEz-lkp@intel.com/
P.S. Is it objtool issue or kernel issue? (Just thinking/questioning loudly)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-06-11 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 18:48 Andy Shevchenko
2024-06-07 13:48 ` kernel test robot
2024-06-11 15:55 ` Andy Shevchenko [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=ZmhzZJdK9IgBYauE@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=chenhuacai@loongson.cn \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seanjc@google.com \
--cc=tangyouling@loongson.cn \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®