From: kernel test robot <yujie.liu@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: <kbuild-all@lists.01.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [ammarfaizi2-block:dhowells/linux-fs/cifs-for-viro 5/8] fs/cifs/cifssmb.c: cifsfs.h is included more than once.
Date: Tue, 12 Jul 2022 14:53:48 +0800 [thread overview]
Message-ID: <617726d5-d261-adfa-d052-ec02b6e8c0e6@intel.com> (raw)
In-Reply-To: <202207100924.Zh7upmAa-lkp@intel.com>
tree: https://github.com/ammarfaizi2/linux-block dhowells/linux-fs/cifs-for-viro
head: 48e2f381e50cded57926128a7743a21573130f46
commit: d04aeaeed153b194dbc7d67525a59df325f2ce21 [5/8] cifs: Change the I/O paths to use an iterator rather than a page list
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <yujie.liu@intel.com>
includecheck warnings: (new ones prefixed by >>)
>> fs/cifs/cifssmb.c: cifsfs.h is included more than once.
^1da177e4c3f4 (Linus Torvalds 2005-04-16 15:20:36 -0700 26) #include "cifspdu.h"
d04aeaeed153b (David Howells 2022-01-24 21:13:24 +0000 @27) #include "cifsfs.h"
^1da177e4c3f4 (Linus Torvalds 2005-04-16 15:20:36 -0700 28) #include "cifsglob.h"
d0d66c443aefa (Shirish Pargaonkar 2007-10-03 18:22:19 +0000 29) #include "cifsacl.h"
^1da177e4c3f4 (Linus Torvalds 2005-04-16 15:20:36 -0700 30) #include "cifsproto.h"
2d2808947f7ea (David Howells 2022-04-06 19:41:28 +0100 @31) #include "cifsfs.h"
^1da177e4c3f4 (Linus Torvalds 2005-04-16 15:20:36 -0700 32) #include "cifs_unicode.h"
--
0-DAY CI Kernel Test Service
https://01.org/lkp
parent reply other threads:[~2022-07-12 6:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <202207100924.Zh7upmAa-lkp@intel.com>]
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=617726d5-d261-adfa-d052-ec02b6e8c0e6@intel.com \
--to=yujie.liu@intel.com \
--cc=dhowells@redhat.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®