From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 2/42] ./usr/include/linux/mtk-fd-v4l2-controls.h:2:1: warning: // comments are not allowed in this language
Date: Sun, 20 Oct 2024 23:55:26 +0800 [thread overview]
Message-ID: <202410202332.mmNWEuLi-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: f80404ea0956d01dcbcdfb1e4807883883fb46bb
commit: 0515dc9d2fe28a3991e1f425fe2f48cb657841ee [2/42] BACKPORT: FROMLIST: media: platform: mediatek: isp: Add Mediatek FD driver
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20241020/202410202332.mmNWEuLi-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241020/202410202332.mmNWEuLi-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/202410202332.mmNWEuLi-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from <built-in>:1:
>> ./usr/include/linux/mtk-fd-v4l2-controls.h:2:1: warning: // comments are not allowed in this language [-Wcomment]
2 | //
| ^
1 warning generated.
usr/include/linux/mtk-fd-v4l2-controls.h:21: found __[us]{8,16,32,64} type without #include <linux/types.h>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-20 15: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=202410202332.mmNWEuLi-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.