From: kernel test robot <lkp@intel.com>
To: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Alex Deucher <alexander.deucher@amd.com>,
Harry Wentland <harry.wentland@amd.com>
Subject: [linux-next:master 7365/10848] htmldocs: ./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:623: warning: Incorrect use of kernel-doc format: * @replay mode: Replay supported
Date: Fri, 18 Aug 2023 03:29:06 +0800 [thread overview]
Message-ID: <202308180330.ylzpuj1m-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 47762f08697484cf0c2f2904b8c52375ed26c8cb
commit: ec8e59cb4e0c1a52d5a541fff9dcec398b48f7b4 [7365/10848] drm/amd/display: Get replay info from VSDB
reproduce: (https://download.01.org/0day-ci/archive/20230818/202308180330.ylzpuj1m-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/202308180330.ylzpuj1m-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> ./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:623: warning: Incorrect use of kernel-doc format: * @replay mode: Replay supported
>> ./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:626: warning: Function parameter or member 'replay_mode' not described in 'amdgpu_hdmi_vsdb_info'
vim +623 ./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h
592
593 /**
594 * struct amdgpu_hdmi_vsdb_info - Keep track of the VSDB info
595 *
596 * AMDGPU supports FreeSync over HDMI by using the VSDB section, and this
597 * struct is useful to keep track of the display-specific information about
598 * FreeSync.
599 */
600 struct amdgpu_hdmi_vsdb_info {
601 /**
602 * @amd_vsdb_version: Vendor Specific Data Block Version, should be
603 * used to determine which Vendor Specific InfoFrame (VSIF) to send.
604 */
605 unsigned int amd_vsdb_version;
606
607 /**
608 * @freesync_supported: FreeSync Supported.
609 */
610 bool freesync_supported;
611
612 /**
613 * @min_refresh_rate_hz: FreeSync Minimum Refresh Rate in Hz.
614 */
615 unsigned int min_refresh_rate_hz;
616
617 /**
618 * @max_refresh_rate_hz: FreeSync Maximum Refresh Rate in Hz
619 */
620 unsigned int max_refresh_rate_hz;
621
622 /**
> 623 * @replay mode: Replay supported
624 */
625 bool replay_mode;
> 626 };
627
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-17 19:30 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=202308180330.ylzpuj1m-lkp@intel.com \
--to=lkp@intel.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=alexander.deucher@amd.com \
--cc=harry.wentland@amd.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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