From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [viro-vfs:work.alpha 5/8] arch/alpha/kernel/io.c:655:1: error: redefinition of 'scr_memcpyw'
Date: Sun, 28 Jan 2024 21:15:44 +0000 [thread overview]
Message-ID: <20240128211544.GD2087318@ZenIV> (raw)
In-Reply-To: <202401280650.Us2Lrkgl-lkp@intel.com>
On Sun, Jan 28, 2024 at 06:59:08AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.alpha
> head: 267674e3b4fd1ff6cedf9b22cd304daa75297966
> commit: 1fb71c4d2bcacd6510fbe411016475ccc15b1a03 [5/8] alpha: missing includes
> config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20240128/202401280650.Us2Lrkgl-lkp@intel.com/config)
> compiler: alpha-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240128/202401280650.Us2Lrkgl-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/202401280650.Us2Lrkgl-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> arch/alpha/kernel/io.c:655:1: error: redefinition of 'scr_memcpyw'
> 655 | scr_memcpyw(u16 *d, const u16 *s, unsigned int count)
> | ^~~~~~~~~~~
> In file included from arch/alpha/kernel/io.c:10:
> include/linux/vt_buffer.h:42:20: note: previous definition of 'scr_memcpyw' with type 'void(u16 *, const u16 *, unsigned int)' {aka 'void(short unsigned int *, const short unsigned int *, unsigned int)'}
> 42 | static inline void scr_memcpyw(u16 *d, const u16 *s, unsigned int count)
> | ^~~~~~~~~~~
_Very_ interesting. First of all, there are 3 users of scr_memcpyw() -
vt.c, vgacon.c and fbcon.c. All of them are getting that thing via
vt_buffer.h. There we have
* include of asm/vga.h, conditional upon VGA_CONSOLE | MDA_CONSOLE
* fallback definitions of scr_...() stuff, conditional upon the
corresponding VT_BUF_HAVE_... not being defined.
The thing is, VT_BUF_HAVE_... are defined in asm/vga.h, so if you don't
have VGA_CONSOLE or MDA_CONSOLE you are going to get the default ones.
In case of scr_memcpyw() it's going to end up with memcpy(); on alpha
that does *not* match the native scr_memcpyw() instance.
Since we have vga.h in mandatory-y, with asm-generic fallback being
reasonable enough... Should that include of asm/vga.h be conditional
in the first place?
I'm really unfamiliar with that thing - the last time I'd looked at
anything related to virtual console had been back in '99 or so...
next prev parent reply other threads:[~2024-01-28 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 22:59 [viro-vfs:work.alpha 5/8] arch/alpha/kernel/io.c:655:1: error: redefinition of 'scr_memcpyw' kernel test robot
2024-01-28 21:15 ` Al Viro [this message]
2024-01-28 21:55 ` Linus Torvalds
2024-01-28 22:09 ` Al Viro
2024-01-28 22:39 ` Linus Torvalds
2024-01-29 2:13 ` Al Viro
2024-01-29 5:03 ` Al Viro
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=20240128211544.GD2087318@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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