linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <rong.a.chen@intel.com>
To: Abhinav Kumar <abhinavk@codeaurora.org>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Rob Clark <robdclark@chromium.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: [linux-next:master 3856/8019] drivers/gpu/drm/selftests/test-drm_framebuffer.c:11:1: iwyu: warning: superfluous #include <drm/drm_print.h>
Date: Wed, 9 Jun 2021 20:03:32 +0800	[thread overview]
Message-ID: <20210609120331.GC237458@shao2-debian> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   ab5803bc555fe68b9b0d37b9a850d3ec601b938a
commit: 1ce05bb86407c54bf4c6a3f9fac0c18164bcf34d [3856/8019] drm: allow drm_atomic_print_state() to accept any drm_printer
config: x86_64-randconfig-b001-20210608 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project d32cc150feb72f315a5bbd34f92e7beca21a50da)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install x86_64 cross compiling tool for clang build
        # apt-get install binutils-x86-64-linux-gnu
        # apt-get install iwyu # include-what-you-use
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=1ce05bb86407c54bf4c6a3f9fac0c18164bcf34d
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 1ce05bb86407c54bf4c6a3f9fac0c18164bcf34d
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross C=1 CHECK=iwyu ARCH=x86_64 

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


iwyu warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/selftests/test-drm_framebuffer.c:11:1: iwyu: warning: superfluous #include <drm/drm_print.h>

vim +11 drivers/gpu/drm/selftests/test-drm_framebuffer.c

54ccae0c08929f Sam Ravnborg  2019-07-16   7  
54ccae0c08929f Sam Ravnborg  2019-07-16   8  #include <drm/drm_device.h>
54ccae0c08929f Sam Ravnborg  2019-07-16   9  #include <drm/drm_mode.h>
54ccae0c08929f Sam Ravnborg  2019-07-16  10  #include <drm/drm_fourcc.h>
1ce05bb86407c5 Abhinav Kumar 2021-04-16 @11  #include <drm/drm_print.h>
54ccae0c08929f Sam Ravnborg  2019-07-16  12  

---
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: 31537 bytes --]

[-- Attachment #3: Type: text/plain, Size: 149 bytes --]

_______________________________________________
kbuild mailing list -- kbuild@lists.01.org
To unsubscribe send an email to kbuild-leave@lists.01.org

                 reply	other threads:[~2021-06-09 12:03 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=20210609120331.GC237458@shao2-debian \
    --to=rong.a.chen@intel.com \
    --cc=abhinavk@codeaurora.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=robdclark@chromium.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