From: kernel test robot <lkp@intel.com>
To: Srish Srinivasan <ssrish@linux.ibm.com>,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Cc: oe-kbuild-all@lists.linux.dev, maddy@linux.ibm.com,
mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu,
James.Bottomley@hansenpartnership.com, jarkko@kernel.org,
zohar@linux.ibm.com, nayna@linux.ibm.com, rnsastry@linux.ibm.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, ssrish@linux.ibm.com
Subject: Re: [PATCH 2/6] powerpc/pseries: move the PLPKS config inside its own sysfs directory
Date: Sun, 14 Dec 2025 02:21:12 +0800 [thread overview]
Message-ID: <202512140150.PUqCvp88-lkp@intel.com> (raw)
In-Reply-To: <20251213052618.190691-3-ssrish@linux.ibm.com>
Hi Srish,
kernel test robot noticed the following build warnings:
[auto build test WARNING on powerpc/next]
[also build test WARNING on powerpc/fixes zohar-integrity/next-integrity linus/master v6.18 next-20251212]
[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/Srish-Srinivasan/pseries-plpks-fix-kernel-doc-comment-inconsistencies/20251213-132948
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
patch link: https://lore.kernel.org/r/20251213052618.190691-3-ssrish%40linux.ibm.com
patch subject: [PATCH 2/6] powerpc/pseries: move the PLPKS config inside its own sysfs directory
config: powerpc-allnoconfig (https://download.01.org/0day-ci/archive/20251214/202512140150.PUqCvp88-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251214/202512140150.PUqCvp88-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/202512140150.PUqCvp88-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/powerpc/kernel/prom.c:59:
>> arch/powerpc/include/asm/plpks.h:118:12: warning: 'plpks_config_create_softlink' defined but not used [-Wunused-function]
118 | static int plpks_config_create_softlink(struct kobject *from) { return 0; }
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/plpks_config_create_softlink +118 arch/powerpc/include/asm/plpks.h
111
112 int plpks_config_create_softlink(struct kobject *from);
113 #else // CONFIG_PSERIES_PLPKS
114 static inline bool plpks_is_available(void) { return false; }
115 static inline u16 plpks_get_passwordlen(void) { BUILD_BUG(); }
116 static inline void plpks_early_init_devtree(void) { }
117 static inline int plpks_populate_fdt(void *fdt) { BUILD_BUG(); }
> 118 static int plpks_config_create_softlink(struct kobject *from) { return 0; }
119 #endif // CONFIG_PSERIES_PLPKS
120
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-12-13 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 5:26 [PATCH 0/6] Extend "trusted" keys to support a new trust source named the PowerVM Key Wrapping Module (PKWM) Srish Srinivasan
2025-12-13 5:26 ` [PATCH 1/6] pseries/plpks: fix kernel-doc comment inconsistencies Srish Srinivasan
2025-12-13 5:26 ` [PATCH 2/6] powerpc/pseries: move the PLPKS config inside its own sysfs directory Srish Srinivasan
2025-12-13 18:21 ` kernel test robot [this message]
2025-12-13 5:26 ` [PATCH 3/6] pseries/plpks: expose PowerVM wrapping features via the sysfs Srish Srinivasan
2025-12-13 5:26 ` [PATCH 4/6] pseries/plpks: add HCALLs for PowerVM Key Wrapping Module Srish Srinivasan
2025-12-13 5:26 ` [PATCH 5/6] keys/trusted_keys: establish PKWM as a trusted source Srish Srinivasan
2025-12-13 19:22 ` Jarkko Sakkinen
2025-12-17 5:18 ` Srish Srinivasan
2025-12-13 5:26 ` [PATCH 6/6] docs: trusted-encryped: add PKWM as a new trust source Srish Srinivasan
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=202512140150.PUqCvp88-lkp@intel.com \
--to=lkp@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=christophe.leroy@csgroup.eu \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=nayna@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rnsastry@linux.ibm.com \
--cc=ssrish@linux.ibm.com \
--cc=zohar@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).