All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Daniel Stone <daniels@collabora.com>,
	Maxime Ripard <mripard@kernel.org>
Subject: [linux-next:master 306/7584] Warning: drivers/gpu/drm/tests/drm_bridge_test.c:126 struct member 'in_fmt' not described in 'fmt_tuple'
Date: Sat, 18 Jul 2026 21:55:07 +0800	[thread overview]
Message-ID: <202607182137.NZSc12Su-lkp@intel.com> (raw)

Hi Nicolas,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   0718283ab28bc3907e10b61a6b4be6fefa1cbb2f
commit: 082fbc179c012d2ab441575f1d9386088c0c88be [306/7584] drm/tests: bridge: Add KUnit tests for bridge chain format selection
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20260718/202607182137.NZSc12Su-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260718/202607182137.NZSc12Su-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/202607182137.NZSc12Su-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: drivers/gpu/drm/tests/drm_bridge_test.c:126 struct member 'in_fmt' not described in 'fmt_tuple'
>> Warning: drivers/gpu/drm/tests/drm_bridge_test.c:126 struct member 'out_fmt' not described in 'fmt_tuple'
>> Warning: drivers/gpu/drm/tests/drm_bridge_test.c:126 struct member 'in_fmt' not described in 'fmt_tuple'
>> Warning: drivers/gpu/drm/tests/drm_bridge_test.c:126 struct member 'out_fmt' not described in 'fmt_tuple'

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-07-18 13:55 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=202607182137.NZSc12Su-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=daniels@collabora.com \
    --cc=mripard@kernel.org \
    --cc=nicolas.frattaroli@collabora.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.