linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org
Subject: cc1: warning: drivers/staging/media/atomisp//pci/hive_isp_css_include/memory_access/: No such file or directory
Date: Sat, 20 Jun 2020 16:06:50 +0800	[thread overview]
Message-ID: <202006201645.1hKeArpT%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2362 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   4333a9b0b67bb4e8bcd91bdd80da80b0ec151162
commit: 08fef4fa947ba75cbf59d67c6be75223c6471a88 media: atomisp: get rid of memory_access.c
date:   9 days ago
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce (this is a W=1 build):
        git checkout 08fef4fa947ba75cbf59d67c6be75223c6471a88
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>, old ones prefixed by <<):

>> cc1: warning: drivers/staging/media/atomisp//pci/hive_isp_css_include/memory_access/: No such file or directory [-Wmissing-include-dirs]
--
>> cc1: warning: drivers/staging/media/atomisp//pci/hive_isp_css_include/memory_access/: No such file or directory [-Wmissing-include-dirs]
In file included from include/linux/uuid.h:12,
from include/linux/mod_devicetable.h:13,
from include/linux/pci.h:27,
from drivers/staging/media/atomisp/pci/atomisp_ioctl.c:21:
In function 'strncpy',
inlined from 'atomisp_enum_input' at drivers/staging/media/atomisp/pci/atomisp_ioctl.c:575:2:
include/linux/string.h:282:9: warning: '__builtin_strncpy' output may be truncated copying 31 bytes from a string of length 31 [-Wstringop-truncation]
282 |  return __builtin_strncpy(p, q, size);
|         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function 'strncpy',
inlined from 'atomisp_enum_input' at drivers/staging/media/atomisp/pci/atomisp_ioctl.c:595:4:
include/linux/string.h:282:9: warning: '__builtin_strncpy' output may be truncated copying between 1 and 30 bytes from a string of length 31 [-Wstringop-truncation]
282 |  return __builtin_strncpy(p, q, size);
|         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
>> cc1: warning: drivers/staging/media/atomisp//pci/hive_isp_css_include/memory_access/: No such file or directory [-Wmissing-include-dirs]
drivers/staging/media/atomisp/pci/atomisp_v4l2.c:762:12: warning: 'atomisp_mrfld_power' defined but not used [-Wunused-function]
762 | static int atomisp_mrfld_power(struct atomisp_device *isp, bool enable)
|            ^~~~~~~~~~~~~~~~~~~

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 73119 bytes --]

                 reply	other threads:[~2020-06-20  8:10 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=202006201645.1hKeArpT%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).