All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Janne Grunau <j@jannau.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [asahilinux:pr/186 9/9] drivers/gpu/drm/apple/dcp.c:455:2: warning: add explicit braces to avoid dangling else
Date: Tue, 12 Sep 2023 07:01:15 +0800	[thread overview]
Message-ID: <202309120640.fKUAz3Jc-lkp@intel.com> (raw)

tree:   https://github.com/AsahiLinux/linux pr/186
head:   4030a6363f99fa38544b1556016ce71676406070
commit: 4030a6363f99fa38544b1556016ce71676406070 [9/9] drm: apple: Update supported firmware versions to 12.3 and 13.5
config: arm64-randconfig-r006-20230912 (https://download.01.org/0day-ci/archive/20230912/202309120640.fKUAz3Jc-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230912/202309120640.fKUAz3Jc-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/202309120640.fKUAz3Jc-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/apple/dcp.c:455:2: warning: add explicit braces to avoid dangling else [-Wdangling-else]
           else if (strncmp(compat_str, "13.5.0", sizeof(compat_str)) == 0)
           ^
   1 warning generated.


vim +455 drivers/gpu/drm/apple/dcp.c

   427	
   428	static enum dcp_firmware_version dcp_check_firmware_version(struct device *dev)
   429	{
   430		char compat_str[DCP_FW_VERSION_STR_LEN];
   431		char fw_str[DCP_FW_VERSION_STR_LEN];
   432		int ret;
   433	
   434		/* firmware version is just informative */
   435		dcp_read_fw_version(dev, "apple,firmware-version", fw_str);
   436	
   437		ret = dcp_read_fw_version(dev, "apple,firmware-compat", compat_str);
   438		if (ret < 0) {
   439			dev_err(dev, "Could not read 'apple,firmware-compat': %d\n", ret);
   440			return DCP_FIRMWARE_UNKNOWN;
   441		}
   442	
   443		if (strncmp(compat_str, "12.3.0", sizeof(compat_str)) == 0)
   444			return DCP_FIRMWARE_V_12_3;
   445		/*
   446		 * m1n1 reports firmware version 13.5 as compatible with 13.3. This is
   447		 * only true for the iomfb endpoint. The interface for the dptx-port
   448		 * endpoint changed between 13.3 and 13.5. The driver will only support
   449		 * firmware 13.5. Check the actual firmware version for compat version
   450		 * 13.3 until m1n1 reports 13.5 as "firmware-compat".
   451		 */
   452		else if (strncmp(compat_str, "13.3.0", sizeof(compat_str)) == 0)
   453			if (strncmp(fw_str, "13.5.0", sizeof(compat_str)) == 0)
   454				return DCP_FIRMWARE_V_13_5;
 > 455		else if (strncmp(compat_str, "13.5.0", sizeof(compat_str)) == 0)
   456			return DCP_FIRMWARE_V_13_5;
   457	
   458		dev_err(dev, "DCP firmware-compat %s (FW: %s) is not supported\n",
   459			compat_str, fw_str);
   460	
   461		return DCP_FIRMWARE_UNKNOWN;
   462	}
   463	

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

                 reply	other threads:[~2023-09-11 23:01 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=202309120640.fKUAz3Jc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=j@jannau.net \
    --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.