All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [djiang:cxl-qtg 8/27] lib/fw_table.c:59:3: error: expected expression
Date: Sat, 27 May 2023 15:25:23 +0800	[thread overview]
Message-ID: <202305271540.oiKyDRcZ-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/djiang/linux.git cxl-qtg
head:   36e73b13967bf8146fe28cc8bea6706944eb564c
commit: b7e30c45269bc274639656da29b2692c64d25455 [8/27] lib/firmware_table: tables: Add CDAT table parsing support
config: i386-randconfig-r033-20230525 (https://download.01.org/0day-ci/archive/20230527/202305271540.oiKyDRcZ-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
        mkdir -p ~/bin
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/djiang/linux.git/commit/?id=b7e30c45269bc274639656da29b2692c64d25455
        git remote add djiang https://git.kernel.org/pub/scm/linux/kernel/git/djiang/linux.git
        git fetch --no-tags djiang cxl-qtg
        git checkout b7e30c45269bc274639656da29b2692c64d25455
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=i386 olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202305271540.oiKyDRcZ-lkp@intel.com/

All errors (new ones prefixed by >>):

>> lib/fw_table.c:59:3: error: expected expression
                   __le16 length = (__force __le16)entry->hdr->cdat.length;
                   ^
>> lib/fw_table.c:61:22: error: use of undeclared identifier 'length'
                   return le16_to_cpu(length);
                                      ^
   include/linux/byteorder/generic.h:91:21: note: expanded from macro 'le16_to_cpu'
   #define le16_to_cpu __le16_to_cpu
                       ^
   2 errors generated.


vim +59 lib/fw_table.c

    45	
    46	static unsigned long __init_or_fwtbllib
    47	fwtbl_get_entry_length(struct fwtbl_subtable_entry *entry)
    48	{
    49		switch (entry->type) {
    50		case ACPI_SUBTABLE_COMMON:
    51			return entry->hdr->common.length;
    52		case ACPI_SUBTABLE_HMAT:
    53			return entry->hdr->hmat.length;
    54		case ACPI_SUBTABLE_PRMT:
    55			return entry->hdr->prmt.length;
    56		case ACPI_SUBTABLE_CEDT:
    57			return entry->hdr->cedt.length;
    58		case CDAT_SUBTABLE:
  > 59			__le16 length = (__force __le16)entry->hdr->cdat.length;
    60	
  > 61			return le16_to_cpu(length);
    62		}
    63		return 0;
    64	}
    65	

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

                 reply	other threads:[~2023-05-27  7:25 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=202305271540.oiKyDRcZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dave.jiang@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.