Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Himanshu Chauhan <hchauhan@ventanamicro.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Anup Patel <anup@brainfault.org>
Subject: [avpatel:riscv_raid6_rvv_v5 71/73] drivers/acpi/apei/apei-base.c:578: warning: Function parameter or struct member 'access_bit_width' not described in 'arch_apei_ffh_read'
Date: Sun, 25 May 2025 22:50:52 +0800	[thread overview]
Message-ID: <202505252252.IrLUtlFg-lkp@intel.com> (raw)

tree:   https://github.com/avpatel/linux.git riscv_raid6_rvv_v5
head:   43edddc0c506de31b78ddf9074e7b2c057e668a7
commit: bbd0c6fe3c7a582057ffa9bb1366c7f699dcd006 [71/73] ACPI: APEI: add FFP support for APEI register access
config: i386-buildonly-randconfig-002-20250525 (https://download.01.org/0day-ci/archive/20250525/202505252252.IrLUtlFg-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250525/202505252252.IrLUtlFg-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/202505252252.IrLUtlFg-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/acpi/apei/apei-base.c:578: warning: Function parameter or struct member 'access_bit_width' not described in 'arch_apei_ffh_read'
>> drivers/acpi/apei/apei-base.c:592: warning: Function parameter or struct member 'access_bit_width' not described in 'arch_apei_ffh_write'


vim +578 drivers/acpi/apei/apei-base.c

   567	
   568	/**
   569	 * arch_apei_ffh_read() - Read FFH register
   570	 * @reg:	FFH encoded register information
   571	 * @val:	place holder for return value
   572	 *
   573	 * Read value from a specified encoded address
   574	 *
   575	 * Return: 0 for success and error code
   576	 */
   577	int __weak arch_apei_ffh_read(u64 reg, u64 *val, u32 access_bit_width)
 > 578	{
   579		return -ENOTSUPP;
   580	}
   581	
   582	/**
   583	 * arch_apei_ffh_write() - Write FFH register
   584	 * @reg:	FFH encoded register information
   585	 * @val:	value to write
   586	 *
   587	 * Write value to a specified address.
   588	 *
   589	 * Return: 0 for success and error code
   590	 */
   591	int __weak arch_apei_ffh_write(u64 reg, u64 val, u32 access_bit_width)
 > 592	{
   593		return -ENOTSUPP;
   594	}
   595	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-05-25 14:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202505252252.IrLUtlFg-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=anup@brainfault.org \
    --cc=hchauhan@ventanamicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox