From: kernel test robot <lkp@intel.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Maxime Ripard <mripard@kernel.org>
Subject: drivers/gpu/drm/tests/drm_kunit_helpers.c:324: warning: bad line: for a KUnit test
Date: Fri, 3 Jan 2025 20:03:25 +0800 [thread overview]
Message-ID: <202501032001.O6WY1VCW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0bc21e701a6ffacfdde7f04f87d664d82e8a13bf
commit: caa714f86699bcfb01aa2d698db12d91af7d0d81 drm/tests: helpers: Add helper for drm_display_mode_from_cea_vic()
date: 9 weeks ago
config: csky-randconfig-051-20240716 (https://download.01.org/0day-ci/archive/20250103/202501032001.O6WY1VCW-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250103/202501032001.O6WY1VCW-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/202501032001.O6WY1VCW-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/tests/drm_kunit_helpers.c:324: warning: bad line: for a KUnit test
vim +324 drivers/gpu/drm/tests/drm_kunit_helpers.c
321
322 /**
323 * drm_kunit_display_mode_from_cea_vic() - return a mode for CEA VIC
> 324 for a KUnit test
325 * @test: The test context object
326 * @dev: DRM device
327 * @video_code: CEA VIC of the mode
328 *
329 * Creates a new mode matching the specified CEA VIC for a KUnit test.
330 *
331 * Resources will be cleaned up automatically.
332 *
333 * Returns: A new drm_display_mode on success or NULL on failure
334 */
335 struct drm_display_mode *
336 drm_kunit_display_mode_from_cea_vic(struct kunit *test, struct drm_device *dev,
337 u8 video_code)
338 {
339 struct drm_display_mode *mode;
340 int ret;
341
342 mode = drm_display_mode_from_cea_vic(dev, video_code);
343 if (!mode)
344 return NULL;
345
346 ret = kunit_add_action_or_reset(test,
347 kunit_action_drm_mode_destroy,
348 mode);
349 if (ret)
350 return NULL;
351
352 return mode;
353 }
354 EXPORT_SYMBOL_GPL(drm_kunit_display_mode_from_cea_vic);
355
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-03 12:04 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=202501032001.O6WY1VCW-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ruanjinjie@huawei.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.