From: kernel test robot <lkp@intel.com>
To: Venkateshwar Rao Gannavarapu <venkateshwar.rao.gannavarapu@xilinx.com>
Cc: oe-kbuild-all@lists.linux.dev, git@amd.com,
Michal Simek <monstr@monstr.eu>
Subject: [xilinx-xlnx:xlnx_rebase_v6.1_LTS_2023.1_update 88/1079] drivers/staging/xlnx_tsmux/xlnx_mpg2tsmux.c:147: warning: expecting prototype for struct strm_node. Prototype was for struct stream_context_node instead
Date: Thu, 15 Jun 2023 00:34:08 +0800 [thread overview]
Message-ID: <202306150002.LtyhxE4e-lkp@intel.com> (raw)
Hi Venkateshwar,
FYI, the error/warning still remains.
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v6.1_LTS_2023.1_update
head: b8d15414a440db0904ee32f03268e2d262dbf397
commit: 94ece3554bcf455d4f036547a7030a774bbeec9c [88/1079] staging: xlnx_tsmux: Initial version of xlnx mpeg2tsmux driver
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20230615/202306150002.LtyhxE4e-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
# https://github.com/Xilinx/linux-xlnx/commit/94ece3554bcf455d4f036547a7030a774bbeec9c
git remote add xilinx-xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xilinx-xlnx xlnx_rebase_v6.1_LTS_2023.1_update
git checkout 94ece3554bcf455d4f036547a7030a774bbeec9c
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 olddefconfig
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/clk/ drivers/gpu/drm/xlnx/ drivers/media/platform/xilinx/ drivers/net/ethernet/xilinx/ drivers/of/ drivers/staging/
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/202306150002.LtyhxE4e-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/staging/xlnx_tsmux/xlnx_mpg2tsmux.c:147: warning: expecting prototype for struct strm_node. Prototype was for struct stream_context_node instead
>> drivers/staging/xlnx_tsmux/xlnx_mpg2tsmux.c:161: warning: expecting prototype for struct strm_info. Prototype was for struct stream_info instead
vim +147 drivers/staging/xlnx_tsmux/xlnx_mpg2tsmux.c
124
125 /**
126 * struct strm_node - struct to describe stream node in linked list
127 * @node_number: node number to handle streams
128 * @node_status: status of stream node
129 * @element: stream context info
130 * @error_code: error codes
131 * @reserved1: reserved bits for hardware align
132 * @tail_pointer: physical address of next stream node in linked list
133 * @strm_phy_addr: physical address of stream context
134 * @node: struct of linked list head
135 * @reserved2: reserved for hardware align
136 */
137 struct stream_context_node {
138 u32 node_number;
139 enum node_status_info node_status;
140 struct stream_context element;
141 enum stream_errors error_code;
142 u32 reserved1;
143 u64 tail_pointer;
144 u64 strm_phy_addr;
145 struct list_head node;
146 u64 reserved2;
> 147 };
148
149 /**
150 * struct strm_info - struct to describe streamid node in streamid table
151 * @pid: identification number of stream
152 * @continuity_counter: counter to maintain packet count for a stream
153 * @usageflag: flag to know free or under use for allocating streamid node
154 * @strmtbl_update: struct to know enqueue or dequeue streamid in table
155 */
156 struct stream_info {
157 u16 pid;
158 u8 continuity_counter;
159 bool usageflag;
160 enum strmtbl_cnxt strmtbl_update;
> 161 };
162
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-14 16:35 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=202306150002.LtyhxE4e-lkp@intel.com \
--to=lkp@intel.com \
--cc=git@amd.com \
--cc=monstr@monstr.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=venkateshwar.rao.gannavarapu@xilinx.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.