From: kernel test robot <lkp@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Uma Shankar" <uma.shankar@intel.com>
Subject: [linux-next:master 10266/10830] drivers/gpu/drm/display/drm_dp_tunnel.c:1185: warning: expecting prototype for drm_dp_tunnel_atomic_get_allocated_bw(). Prototype was for drm_dp_tunnel_get_allocated_bw() instead
Date: Wed, 28 Feb 2024 19:40:18 +0800 [thread overview]
Message-ID: <202402281921.GR4Yw253-lkp@intel.com> (raw)
Hi Imre,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 20af1ca418d2c0b11bc2a1fe8c0c88f67bcc2a7e
commit: 91888b5b1ad2fda3f4c6b8de5dd42dbe8b90ac2c [10266/10830] drm/i915/dp: Add support for DP tunnel BW allocation
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20240228/202402281921.GR4Yw253-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240228/202402281921.GR4Yw253-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/202402281921.GR4Yw253-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/display/drm_dp_tunnel.c:447: warning: Function parameter or struct member 'tunnel' not described in 'drm_dp_tunnel_put'
>> drivers/gpu/drm/display/drm_dp_tunnel.c:447: warning: Function parameter or struct member 'tracker' not described in 'drm_dp_tunnel_put'
>> drivers/gpu/drm/display/drm_dp_tunnel.c:1185: warning: expecting prototype for drm_dp_tunnel_atomic_get_allocated_bw(). Prototype was for drm_dp_tunnel_get_allocated_bw() instead
>> drivers/gpu/drm/display/drm_dp_tunnel.c:1903: warning: Function parameter or struct member 'max_group_count' not described in 'drm_dp_tunnel_mgr_create'
vim +1185 drivers/gpu/drm/display/drm_dp_tunnel.c
295654f7e554a9 Imre Deak 2024-02-26 1171
295654f7e554a9 Imre Deak 2024-02-26 1172 /**
295654f7e554a9 Imre Deak 2024-02-26 1173 * drm_dp_tunnel_atomic_get_allocated_bw - Get the BW allocated for a DP tunnel
295654f7e554a9 Imre Deak 2024-02-26 1174 * @tunnel: Tunnel object
295654f7e554a9 Imre Deak 2024-02-26 1175 *
295654f7e554a9 Imre Deak 2024-02-26 1176 * Get the current BW allocated for @tunnel. After the tunnel is created /
295654f7e554a9 Imre Deak 2024-02-26 1177 * resumed and the BW allocation mode is enabled for it, the allocation
295654f7e554a9 Imre Deak 2024-02-26 1178 * becomes determined only after the first allocation request by the driver
295654f7e554a9 Imre Deak 2024-02-26 1179 * calling drm_dp_tunnel_alloc_bw().
295654f7e554a9 Imre Deak 2024-02-26 1180 *
295654f7e554a9 Imre Deak 2024-02-26 1181 * Return the BW allocated for the tunnel, or -1 if the allocation is
295654f7e554a9 Imre Deak 2024-02-26 1182 * undetermined.
295654f7e554a9 Imre Deak 2024-02-26 1183 */
295654f7e554a9 Imre Deak 2024-02-26 1184 int drm_dp_tunnel_get_allocated_bw(struct drm_dp_tunnel *tunnel)
295654f7e554a9 Imre Deak 2024-02-26 @1185 {
295654f7e554a9 Imre Deak 2024-02-26 1186 return tunnel->allocated_bw;
295654f7e554a9 Imre Deak 2024-02-26 1187 }
295654f7e554a9 Imre Deak 2024-02-26 1188 EXPORT_SYMBOL(drm_dp_tunnel_get_allocated_bw);
295654f7e554a9 Imre Deak 2024-02-26 1189
:::::: The code at line 1185 was first introduced by commit
:::::: 295654f7e554a9f089bdab0b2bb9a9aad7c402c0 drm/dp: Add support for DP tunneling
:::::: TO: Imre Deak <imre.deak@intel.com>
:::::: CC: Imre Deak <imre.deak@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-28 11:40 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=202402281921.GR4Yw253-lkp@intel.com \
--to=lkp@intel.com \
--cc=imre.deak@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@linux.intel.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