From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: kernel test robot <yujie.liu@intel.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
oe-kbuild-all@lists.linux.dev, linux-nilfs@vger.kernel.org
Subject: Re: [konis-nilfs2:for-akpm 4/4] fs/nilfs2/super.c: linux/fs_context.h is included more than once.
Date: Thu, 25 Apr 2024 17:35:22 +0900 [thread overview]
Message-ID: <CAKFNMonbNQJofL7QjgthShSt9y+BCoZOv+cWstDe5LRpAqsu-w@mail.gmail.com> (raw)
In-Reply-To: <202404251450.rttcxC1o-lkp@intel.com>
On Thu, Apr 25, 2024 at 3:48 PM kernel test robot wrote:
>
> tree: https://github.com/konis/nilfs2 for-akpm
> head: 69812977939c7895ede256e122284c19d4d83aef
> commit: 69812977939c7895ede256e122284c19d4d83aef [4/4] nilfs2: convert to use the new mount API
> compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
>
> 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 <yujie.liu@intel.com>
> | Closes: https://lore.kernel.org/r/202404251450.rttcxC1o-lkp@intel.com/
>
> includecheck warnings: (new ones prefixed by >>)
> >> fs/nilfs2/super.c: linux/fs_context.h is included more than once.
Thank you for the report.
This patch has just been added to the -mm unstable tree, but I found
another issue, so I'd like to ask Andrew to remove it once, and will
resend a revised patch that also includes the fix for this warning.
Regards,
Ryusuke Konishi
>
> vim +32 fs/nilfs2/super.c
>
> > 32 #include <linux/fs_context.h>
> 33 #include <linux/fs_parser.h>
> 34 #include <linux/crc32.h>
> 35 #include <linux/vfs.h>
> 36 #include <linux/writeback.h>
> 37 #include <linux/seq_file.h>
> 38 #include <linux/mount.h>
> > 39 #include <linux/fs_context.h>
> 40 #include "nilfs.h"
> 41 #include "export.h"
> 42 #include "mdt.h"
> 43 #include "alloc.h"
> 44 #include "btree.h"
> 45 #include "btnode.h"
> 46 #include "page.h"
> 47 #include "cpfile.h"
> 48 #include "sufile.h" /* nilfs_sufile_resize(), nilfs_sufile_set_alloc_range() */
> 49 #include "ifile.h"
> 50 #include "dat.h"
> 51 #include "segment.h"
> 52 #include "segbuf.h"
> 53
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
prev parent reply other threads:[~2024-04-25 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 6:42 [konis-nilfs2:for-akpm 4/4] fs/nilfs2/super.c: linux/fs_context.h is included more than once kernel test robot
2024-04-25 8:35 ` Ryusuke Konishi [this message]
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=CAKFNMonbNQJofL7QjgthShSt9y+BCoZOv+cWstDe5LRpAqsu-w@mail.gmail.com \
--to=konishi.ryusuke@gmail.com \
--cc=linux-nilfs@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sandeen@redhat.com \
--cc=yujie.liu@intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).