From: kernel test robot <lkp@intel.com>
To: Cong Yang <yangcong5@huaqin.corp-partner.google.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: drivers/gpu/drm/panel/panel-himax-hx83102.c:67: warning: Cannot understand * @width_mm: width of the panel's active display area
Date: Sun, 27 Apr 2025 04:59:41 +0800 [thread overview]
Message-ID: <202504270445.BKZnZEmV-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 02ddfb981de88a2c15621115dd7be2431252c568
commit: 0ef94554dc40fbdb7e57ff90cd1e7fa71e1e89fd drm/panel: himax-hx83102: Break out as separate driver
date: 12 months ago
config: sparc-randconfig-001-20250426 (https://download.01.org/0day-ci/archive/20250427/202504270445.BKZnZEmV-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 10.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250427/202504270445.BKZnZEmV-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/202504270445.BKZnZEmV-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/panel/panel-himax-hx83102.c:67: warning: Cannot understand * @width_mm: width of the panel's active display area
on line 67 - I thought it was a doc line
vim +67 drivers/gpu/drm/panel/panel-himax-hx83102.c
62
63 struct hx83102_panel_desc {
64 const struct drm_display_mode *modes;
65
66 /**
> 67 * @width_mm: width of the panel's active display area
68 * @height_mm: height of the panel's active display area
69 */
70 struct {
71 unsigned int width_mm;
72 unsigned int height_mm;
73 } size;
74
75 int (*init)(struct hx83102 *ctx);
76 };
77
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-26 21:00 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=202504270445.BKZnZEmV-lkp@intel.com \
--to=lkp@intel.com \
--cc=dianders@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yangcong5@huaqin.corp-partner.google.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
all inboxes | Powered by JetHome®