From: kernel test robot <lkp@intel.com>
To: Haren Myneni <haren@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
mpe@ellerman.id.au, npiggin@gmail.com, maddy@linux.ibm.com,
msuchanek@suse.de, tyreld@linux.ibm.com, hbabu@us.ibm.com,
haren@linux.ibm.com
Subject: Re: [PATCH] powerpc/pseries: Add papr-platform-dump character driver for dump retrieval
Date: Tue, 26 Nov 2024 00:43:44 +0800 [thread overview]
Message-ID: <202411260057.wrWAIl67-lkp@intel.com> (raw)
In-Reply-To: <20241124052040.239813-1-haren@linux.ibm.com>
Hi Haren,
kernel test robot noticed the following build warnings:
[auto build test WARNING on powerpc/next]
[also build test WARNING on powerpc/fixes linus/master v6.12 next-20241125]
[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/Haren-Myneni/powerpc-pseries-Add-papr-platform-dump-character-driver-for-dump-retrieval/20241125-112816
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
patch link: https://lore.kernel.org/r/20241124052040.239813-1-haren%40linux.ibm.com
patch subject: [PATCH] powerpc/pseries: Add papr-platform-dump character driver for dump retrieval
config: powerpc64-randconfig-001-20241125 (https://download.01.org/0day-ci/archive/20241126/202411260057.wrWAIl67-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241126/202411260057.wrWAIl67-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/202411260057.wrWAIl67-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/powerpc/platforms/pseries/papr-platform-dump.c:51: warning: Function parameter or struct member 'dump_tag_hi' not described in 'ibm_platform_dump_params'
>> arch/powerpc/platforms/pseries/papr-platform-dump.c:51: warning: Function parameter or struct member 'dump_tag_lo' not described in 'ibm_platform_dump_params'
>> arch/powerpc/platforms/pseries/papr-platform-dump.c:51: warning: Function parameter or struct member 'sequence_hi' not described in 'ibm_platform_dump_params'
>> arch/powerpc/platforms/pseries/papr-platform-dump.c:51: warning: Function parameter or struct member 'sequence_lo' not described in 'ibm_platform_dump_params'
>> arch/powerpc/platforms/pseries/papr-platform-dump.c:51: warning: Function parameter or struct member 'bytes_ret_hi' not described in 'ibm_platform_dump_params'
>> arch/powerpc/platforms/pseries/papr-platform-dump.c:51: warning: Function parameter or struct member 'bytes_ret_lo' not described in 'ibm_platform_dump_params'
>> arch/powerpc/platforms/pseries/papr-platform-dump.c:51: warning: Excess struct member 'dump_tag' description in 'ibm_platform_dump_params'
>> arch/powerpc/platforms/pseries/papr-platform-dump.c:51: warning: Excess struct member 'sequence' description in 'ibm_platform_dump_params'
>> arch/powerpc/platforms/pseries/papr-platform-dump.c:51: warning: Excess struct member 'written' description in 'ibm_platform_dump_params'
vim +51 arch/powerpc/platforms/pseries/papr-platform-dump.c
25
26 /**
27 * struct ibm_platform_dump_params - Parameters (in and out) for
28 * ibm,platform-dump
29 * @work_area: In: work area buffer for results.
30 * @buf_length: In: work area buffer length in bytes
31 * @dump_tag: In: Dump_Tag representing an id of the dump being processed
32 * @sequence: In: Sequence number. Out: Next sequence number.
33 * @written: Out: Bytes written by ibm,platform-dump to @work_area.
34 * @status: Out: RTAS call status.
35 * @list: Maintain the list of dumps are in progress. Can retrieve
36 * multiple dumps with different dump IDs at the same time,
37 * but not with the same dump ID. This list is used to
38 * determine whether the dump for the same ID is in progress.
39 */
40 struct ibm_platform_dump_params {
41 struct rtas_work_area *work_area;
42 u32 buf_length;
43 u32 dump_tag_hi;
44 u32 dump_tag_lo;
45 u32 sequence_hi;
46 u32 sequence_lo;
47 u32 bytes_ret_hi;
48 u32 bytes_ret_lo;
49 s32 status;
50 struct list_head list;
> 51 };
52
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-25 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 5:20 [PATCH] powerpc/pseries: Add papr-platform-dump character driver for dump retrieval Haren Myneni
2024-11-25 16:43 ` kernel test robot [this message]
2024-11-26 19:12 ` Mahesh J Salgaonkar
2024-11-26 20:40 ` Haren Myneni
2024-11-27 9:11 ` Michal Suchánek
2024-12-03 4:40 ` Haren Myneni
2024-12-04 16:57 ` Michal Suchánek
2024-12-05 2:14 ` Haren Myneni
2024-12-05 10:42 ` Michal Suchánek
2024-12-10 9:18 ` Haren Myneni
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=202411260057.wrWAIl67-lkp@intel.com \
--to=lkp@intel.com \
--cc=haren@linux.ibm.com \
--cc=hbabu@us.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=npiggin@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tyreld@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).