Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-acpi@vger.kernel.org, devel@acpica.org,
	linux-pm@vger.kernel.org,
	Mario Limonciello <mario.limonciello@amd.com>
Subject: [rafael-pm:bleeding-edge 91/93] drivers/pinctrl/pinctrl-amd.c:987:2: error: must use 'struct' tag to refer to type 'pinctrl_dev'
Date: Tue, 6 May 2025 16:05:41 +0800	[thread overview]
Message-ID: <202505061622.qVVdwLYk-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge
head:   c6039ca5edc14d1f0b34aa83a37fb7a379d8de46
commit: a2c2d5006579832e53851808f05d1bcf866215ca [91/93] pinctrl: amd: Fix hibernation support with CONFIG_SUSPEND unset
config: x86_64-buildonly-randconfig-001-20250506 (https://download.01.org/0day-ci/archive/20250506/202505061622.qVVdwLYk-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/20250506/202505061622.qVVdwLYk-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/202505061622.qVVdwLYk-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/pinctrl/pinctrl-amd.c:987:2: error: must use 'struct' tag to refer to type 'pinctrl_dev'
     987 |         pinctrl_dev = dev_get_drvdata(dev);
         |         ^
         |         struct 
>> drivers/pinctrl/pinctrl-amd.c:987:14: error: expected identifier or '('
     987 |         pinctrl_dev = dev_get_drvdata(dev);
         |                     ^
   2 errors generated.


vim +987 drivers/pinctrl/pinctrl-amd.c

79d2c8bede2c93 Daniel Drake        2017-09-11  984  
f31f33dbb3bab5 Maciej S. Szmigiero 2025-01-06  985  static int amd_gpio_suspend(struct device *dev)
f31f33dbb3bab5 Maciej S. Szmigiero 2025-01-06  986  {
179db1909c5c4b Mario Limonciello   2025-04-07 @987  	pinctrl_dev = dev_get_drvdata(dev);
f31f33dbb3bab5 Maciej S. Szmigiero 2025-01-06  988  	return amd_gpio_suspend_hibernate_common(dev, true);
f31f33dbb3bab5 Maciej S. Szmigiero 2025-01-06  989  }
f31f33dbb3bab5 Maciej S. Szmigiero 2025-01-06  990  

:::::: The code at line 987 was first introduced by commit
:::::: 179db1909c5c4b5300cce626507b0f843f7d2cc2 pinctrl: amd: Add an LPS0 check() callback

:::::: TO: Mario Limonciello <mario.limonciello@amd.com>
:::::: CC: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

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

                 reply	other threads:[~2025-05-06  8:05 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=202505061622.qVVdwLYk-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=devel@acpica.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mario.limonciello@amd.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rjw@rjwysocki.net \
    /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