From: kernel test robot <lkp@intel.com>
To: Louis Chauvet <louis.chauvet@bootlin.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: drivers/gpu/drm/vkms/vkms_configfs.c:625:5: warning: 'vkms_configfs_parse_next_format' defined but not used
Date: Fri, 14 Aug 2026 14:57:51 +0200 [thread overview]
Message-ID: <202608141459.lTWy7nlR-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Louis-Chauvet/drm-drm_mode_config-Add-helper-to-get-plane-type-name/20260807-092508
head: c4c09a7274b7bb12e10957fc5da78e52e5bbf54d
commit: d799e044e269193685079d3260b0b0b33d17a237 drm/vkms: Introduce configfs for plane format
date: 7 days ago
config: x86_64-rhel-9.4-bpf (https://download.01.org/0day-ci/archive/20260814/202608141459.lTWy7nlR-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260814/202608141459.lTWy7nlR-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/202608141459.lTWy7nlR-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/vkms/vkms_configfs.c:625:5: warning: 'vkms_configfs_parse_next_format' defined but not used [-Wunused-function]
625 | int vkms_configfs_parse_next_format(const char *page, const char *page_end, char **out)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/vkms_configfs_parse_next_format +625 drivers/gpu/drm/vkms/vkms_configfs.c
614
615 /**
616 * vkms_configfs_parse_next_format() - Parse the next format in page,
617 * skipping all non fourcc-related characters
618 * @page: page to search into
619 * @page_end: last character of the page
620 * @out: Output pointer, will point inside page
621 *
622 * Returns: size of the matched format, @out will point to the + or -
623 */
624 VISIBLE_IF_KUNIT
> 625 int vkms_configfs_parse_next_format(const char *page, const char *page_end, char **out)
626 {
627 int count = page - page_end;
628 char *tmp_plus = strnchr(page, count, '+');
629 char *tmp_minus = strnchr(page, count, '-');
630
631 if (!tmp_plus && !tmp_minus)
632 return 0;
633 if (!tmp_plus)
634 *out = tmp_minus;
635 else if (!tmp_minus)
636 *out = tmp_plus;
637 else
638 *out = min(tmp_plus, tmp_minus);
639
640 char *end = *out + 1;
641
642 while (end < page_end) {
643 if (!isalnum(*end) && *end != '*')
644 break;
645 end++;
646 }
647
648 return end - *out;
649 }
650 EXPORT_SYMBOL_IF_KUNIT(vkms_configfs_parse_next_format);
651
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-14 12:58 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=202608141459.lTWy7nlR-lkp@intel.com \
--to=lkp@intel.com \
--cc=louis.chauvet@bootlin.com \
--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 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.