From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>,
kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [arm:for-next 4/4] arch/arm/vfp/vfpmodule.c:324:13: error: static declaration of 'VFP_bounce' follows non-static declaration
Date: Mon, 14 Aug 2023 23:08:25 +0100 [thread overview]
Message-ID: <ZNql2TqaVFnMKlzJ@shell.armlinux.org.uk> (raw)
In-Reply-To: <202308150547.m54XHV12-lkp@intel.com>
On Tue, Aug 15, 2023 at 05:06:03AM +0800, kernel test robot wrote:
> tree: git://git.armlinux.org.uk/~rmk/linux-arm.git for-next
> head: f493fedcc3016e46ecbf7ab9490ba4762723efab
> commit: f493fedcc3016e46ecbf7ab9490ba4762723efab [4/4] Merge branch 'devel-stable' into for-next
> config: arm-milbeaut_m10v_defconfig (https://download.01.org/0day-ci/archive/20230815/202308150547.m54XHV12-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce: (https://download.01.org/0day-ci/archive/20230815/202308150547.m54XHV12-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/202308150547.m54XHV12-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> arch/arm/vfp/vfpmodule.c:324:13: error: static declaration of 'VFP_bounce' follows non-static declaration
> static void VFP_bounce(u32 trigger, u32 fpexc, struct pt_regs *regs)
> ^
> arch/arm/include/asm/vfp.h:105:6: note: previous declaration is here
> void VFP_bounce(u32 trigger, u32 fpexc, struct pt_regs *regs);
> ^
> 1 error generated.
I'm guessing this is a conflict between Arnd's patch
ae1f8d793a19 ("ARM: 9304/1: add prototype for function called only from asm")
merged in v6.5-rc1 and Ard's patch, and that part of Arnd's patch
needs to be reverted since VFP_bounce is now static. Agreed?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>,
kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [arm:for-next 4/4] arch/arm/vfp/vfpmodule.c:324:13: error: static declaration of 'VFP_bounce' follows non-static declaration
Date: Mon, 14 Aug 2023 23:08:25 +0100 [thread overview]
Message-ID: <ZNql2TqaVFnMKlzJ@shell.armlinux.org.uk> (raw)
In-Reply-To: <202308150547.m54XHV12-lkp@intel.com>
On Tue, Aug 15, 2023 at 05:06:03AM +0800, kernel test robot wrote:
> tree: git://git.armlinux.org.uk/~rmk/linux-arm.git for-next
> head: f493fedcc3016e46ecbf7ab9490ba4762723efab
> commit: f493fedcc3016e46ecbf7ab9490ba4762723efab [4/4] Merge branch 'devel-stable' into for-next
> config: arm-milbeaut_m10v_defconfig (https://download.01.org/0day-ci/archive/20230815/202308150547.m54XHV12-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce: (https://download.01.org/0day-ci/archive/20230815/202308150547.m54XHV12-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/202308150547.m54XHV12-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> arch/arm/vfp/vfpmodule.c:324:13: error: static declaration of 'VFP_bounce' follows non-static declaration
> static void VFP_bounce(u32 trigger, u32 fpexc, struct pt_regs *regs)
> ^
> arch/arm/include/asm/vfp.h:105:6: note: previous declaration is here
> void VFP_bounce(u32 trigger, u32 fpexc, struct pt_regs *regs);
> ^
> 1 error generated.
I'm guessing this is a conflict between Arnd's patch
ae1f8d793a19 ("ARM: 9304/1: add prototype for function called only from asm")
merged in v6.5-rc1 and Ard's patch, and that part of Arnd's patch
needs to be reverted since VFP_bounce is now static. Agreed?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-14 22:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 21:06 [arm:for-next 4/4] arch/arm/vfp/vfpmodule.c:324:13: error: static declaration of 'VFP_bounce' follows non-static declaration kernel test robot
2023-08-14 21:06 ` kernel test robot
2023-08-14 22:08 ` Russell King (Oracle) [this message]
2023-08-14 22:08 ` Russell King (Oracle)
2023-08-14 22:15 ` Arnd Bergmann
2023-08-14 22:15 ` Arnd Bergmann
2023-08-15 8:39 ` Ard Biesheuvel
2023-08-15 8:39 ` Ard Biesheuvel
2023-08-15 9:05 ` Russell King (Oracle)
2023-08-15 9:05 ` Russell King (Oracle)
2023-08-15 16:18 ` Ard Biesheuvel
2023-08-15 16:18 ` Ard Biesheuvel
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=ZNql2TqaVFnMKlzJ@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 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.