All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Khai Wen Ng <khai.wen.ng@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, "sys_oak" <sys_oak@intel.com>,
	"Yew, Chang Ching" <chang.ching.yew@intel.com>
Subject: [acrn:6.17/linux 3121/3134] drivers/i2c/i2c-core-acpi.c:321:1: error: label at end of compound statement
Date: Sat, 07 Mar 2026 13:51:44 +0800	[thread overview]
Message-ID: <202603071342.3StYPDF8-lkp@intel.com> (raw)

tree:   https://github.com/projectacrn/acrn-kernel 6.17/linux
head:   d2ae39d099178698dc32d2165a32f4d6d13d107b
commit: f5ccdd6257bea670f612e8bdabe5052d698dd031 [3121/3134] i2c: i2c-core-acpi: clear dependency for MUX or ATR adapters
config: arm64-randconfig-004-20260307 (https://download.01.org/0day-ci/archive/20260307/202603071342.3StYPDF8-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260307/202603071342.3StYPDF8-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/202603071342.3StYPDF8-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/i2c/i2c-core-acpi.c: In function 'i2c_acpi_register_device':
>> drivers/i2c/i2c-core-acpi.c:321:1: error: label at end of compound statement
    err:
    ^~~


vim +321 drivers/i2c/i2c-core-acpi.c

   276	
   277	static void i2c_acpi_register_device(struct i2c_adapter *adapter,
   278					     struct acpi_device *adev,
   279					     struct i2c_board_info *info)
   280	{
   281		/*
   282		 * Skip registration on boards where the ACPI tables are
   283		 * known to contain bogus I2C devices.
   284		 */
   285		if (acpi_quirk_skip_i2c_client_enumeration(adev))
   286			return;
   287	
   288		/* Check if Device is on ATR or MUX adapter */
   289		if (adapter->is_atr || adapter->is_mux) {
   290			u32 channel;
   291	
   292			if (fwnode_property_present(&adev->fwnode, "channel")) {
   293				if (fwnode_property_read_u32(&adev->fwnode, "channel", &channel)) {
   294					dev_err(&adev->dev, "failed to read channel property\n");
   295					return;
   296				}
   297	
   298				if (adapter->chan_id != channel) {
   299					dev_err(&adev->dev, "device is not on current adapter %d\n",
   300						adapter->chan_id);
   301					goto err;
   302				} else {
   303					acpi_dev_clear_dependencies(ACPI_COMPANION(adapter->dev.parent));
   304				}
   305	
   306				if (adev->dep_unmet) {
   307					dev_err(&adev->dev, "device has unmet dependencies\n");
   308					return;
   309				}
   310			} else {
   311				dev_err(&adev->dev, "channel property not present\n");
   312				return;
   313			}
   314		}
   315	
   316		adev->power.flags.ignore_parent = true;
   317		acpi_device_set_enumerated(adev);
   318	
   319		if (IS_ERR(i2c_new_client_device(adapter, info)))
   320			adev->power.flags.ignore_parent = false;
 > 321	err:
   322	}
   323	

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

                 reply	other threads:[~2026-03-07  5:52 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=202603071342.3StYPDF8-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chang.ching.yew@intel.com \
    --cc=khai.wen.ng@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sys_oak@intel.com \
    /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.