From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>, linux-fsdevel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
"Amir Goldstein" <amir73il@gmail.com>,
"Josef Bacik" <josef@toxicpanda.com>,
"Jeff Layton" <jlayton@kernel.org>, "Mike Yuan" <me@yhndnzj.com>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
"Lennart Poettering" <mzxreary@0pointer.de>,
"Aleksa Sarai" <cyphar@cyphar.com>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kara" <jack@suse.cz>, "Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
cgroups@vger.kernel.org, netdev@vger.kernel.org,
"Christian Brauner" <brauner@kernel.org>
Subject: Re: [PATCH 1/3] nstree: make struct ns_tree private
Date: Thu, 25 Sep 2025 06:39:19 +0800 [thread overview]
Message-ID: <202509250641.QU55kXeK-lkp@intel.com> (raw)
In-Reply-To: <20250924-work-namespaces-fixes-v1-1-8fb682c8678e@kernel.org>
Hi Christian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on d969328c513c6679b4be11a995ffd4d184c25b34]
url: https://github.com/intel-lab-lkp/linux/commits/Christian-Brauner/nstree-make-struct-ns_tree-private/20250924-193826
base: d969328c513c6679b4be11a995ffd4d184c25b34
patch link: https://lore.kernel.org/r/20250924-work-namespaces-fixes-v1-1-8fb682c8678e%40kernel.org
patch subject: [PATCH 1/3] nstree: make struct ns_tree private
config: m68k-allnoconfig (https://download.01.org/0day-ci/archive/20250925/202509250641.QU55kXeK-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250925/202509250641.QU55kXeK-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/202509250641.QU55kXeK-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: kernel/nstree.c:17 struct member 'type' not described in 'ns_tree'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-24 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 11:33 [PATCH 0/3] ns: tweak ns common handling Christian Brauner
2025-09-24 11:33 ` [PATCH 1/3] nstree: make struct ns_tree private Christian Brauner
2025-09-24 11:46 ` Jan Kara
2025-09-24 22:39 ` kernel test robot [this message]
2025-09-24 11:33 ` [PATCH 2/3] ns: move ns type into struct ns_common Christian Brauner
2025-09-24 11:58 ` Jan Kara
2025-09-24 11:34 ` [PATCH 3/3] ns: drop assert Christian Brauner
2025-09-24 12:00 ` Jan Kara
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=202509250641.QU55kXeK-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=anna-maria@linutronix.de \
--cc=brauner@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=cyphar@cyphar.com \
--cc=frederic@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=me@yhndnzj.com \
--cc=mkoutny@suse.com \
--cc=mzxreary@0pointer.de \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zbyszek@in.waw.pl \
/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).