From: kernel test robot <lkp@intel.com>
To: Ken Xue <Ken.Xue@amd.com>,
linux-acpi@vger.kernel.org, rafael@kernel.org,
andriy.shevchenko@linux.intel.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev, Ken.Xue@amd.com
Subject: Re: [PATCH] acpi: trigger wakeup key event from power button
Date: Fri, 8 Sep 2023 04:06:17 +0800 [thread overview]
Message-ID: <202309080351.xHt2qhP2-lkp@intel.com> (raw)
In-Reply-To: <20230907074342.7722-1-Ken.Xue@amd.com>
Hi Ken,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on linus/master next-20230907]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ken-Xue/acpi-trigger-wakeup-key-event-from-power-button/20230907-232828
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20230907074342.7722-1-Ken.Xue%40amd.com
patch subject: [PATCH] acpi: trigger wakeup key event from power button
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20230908/202309080351.xHt2qhP2-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/20230908/202309080351.xHt2qhP2-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/202309080351.xHt2qhP2-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/i915/display/intel_lvds.c:30:
>> include/acpi/button.h:11:45: warning: declaration of 'struct acpi_device' will not be visible outside of this function [-Wvisibility]
extern void acpi_power_button_wakeup(struct acpi_device *device);
^
1 warning generated.
vim +11 include/acpi/button.h
8
9 #if IS_ENABLED(CONFIG_ACPI_BUTTON)
10 extern int acpi_lid_open(void);
> 11 extern void acpi_power_button_wakeup(struct acpi_device *device);
12 #else
13 static inline int acpi_lid_open(void)
14 {
15 return 1;
16 }
17 static inline void acpi_power_button_wakeup(struct acpi_device *device)
18 {
19 return;
20 }
21 #endif /* IS_ENABLED(CONFIG_ACPI_BUTTON) */
22
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-07 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 7:43 [PATCH] acpi: trigger wakeup key event from power button Ken Xue
2023-09-07 18:51 ` kernel test robot
2023-09-07 19:34 ` kernel test robot
2023-09-07 20:06 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-08 9:57 Ken Xue
2023-09-11 9:42 ` Andy Shevchenko
2023-09-12 5:32 ` Ken Xue
2023-09-12 9:30 ` Andy Shevchenko
2023-09-12 12:53 ` Ken Xue
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=202309080351.xHt2qhP2-lkp@intel.com \
--to=lkp@intel.com \
--cc=Ken.Xue@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
/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