From: kernel test robot <lkp@intel.com>
To: Ismael Luceno <ismael@iodev.co.uk>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Ismael Luceno <ismael@iodev.co.uk>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
"open list:FILESYSTEMS (VFS and infrastructure)"
<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 3/8] init: let filesystems ask whether they are mounting the root device
Date: Tue, 17 Nov 2026 15:41:48 +0800 [thread overview]
Message-ID: <202611171523.oW7KTbJo-lkp@intel.com> (raw)
In-Reply-To: <20261116224316.11237-13-ismael@iodev.co.uk>
Hi Ismael,
kernel test robot noticed the following build errors:
[auto build test ERROR on kdave/for-next]
[also build test ERROR on btrfs/for-next brauner-vfs/vfs.all linus/master v7.4-rc3 next-20261116]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ismael-Luceno/btrfs-add-config-options-for-the-root-device-scan/20261116-234317
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link: https://lore.kernel.org/r/20261116224316.11237-13-ismael%40iodev.co.uk
patch subject: [PATCH 3/8] init: let filesystems ask whether they are mounting the root device
config: parisc-randconfig-1001-20261117 (https://download.01.org/0day-ci/archive/20261117/202611171523.oW7KTbJo-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261117/202611171523.oW7KTbJo-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/202611171523.oW7KTbJo-lkp@intel.com/
All errors (new ones prefixed by >>):
>> init/do_mounts.c:391:20: error: static declaration of 'is_root_dev' follows non-static declaration
static inline bool is_root_dev(dev_t dev)
^~~~~~~~~~~
In file included from init/do_mounts.c:8:
include/linux/root_dev.h:30:6: note: previous declaration of 'is_root_dev' was here
bool is_root_dev(dev_t dev);
^~~~~~~~~~~
vim +/is_root_dev +391 init/do_mounts.c
390
> 391 static inline bool is_root_dev(dev_t dev)
392 {
393 return false;
394 }
395 #endif /* CONFIG_BLOCK */
396
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-11-17 7:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 22:43 [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd Ismael Luceno
2026-11-16 22:43 ` [PATCH 1/8] btrfs: add config options for the root device scan Ismael Luceno
2026-11-16 22:43 ` [PATCH 2/8] init: mount devtmpfs before the root filesystem Ismael Luceno
2026-11-16 22:43 ` [PATCH 3/8] init: let filesystems ask whether they are mounting the root device Ismael Luceno
2026-11-17 7:41 ` kernel test robot [this message]
2026-11-16 22:43 ` [PATCH 4/8] btrfs: add a helper to scan all block devices Ismael Luceno
2026-11-17 13:10 ` kernel test robot
2026-11-16 22:43 ` [PATCH 5/8] btrfs: wait for the root filesystem to have all its devices Ismael Luceno
2026-11-18 1:19 ` kernel test robot
2026-11-16 22:43 ` [PATCH 6/8] Documentation: btrfs: document waiting for the root filesystem devices Ismael Luceno
2026-11-16 22:43 ` [PATCH 7/8] init: let a filesystem resolve a root device by UUID or label Ismael Luceno
2026-11-16 22:43 ` [PATCH 8/8] btrfs: resolve root=UUID= and root=LABEL= Ismael Luceno
2026-11-16 23:41 ` [PATCH 0/8] btrfs: assemble a multi-device root filesystem without an initrd Qu Wenruo
2026-11-17 17:36 ` Ismael Luceno
2026-11-17 20:00 ` Qu Wenruo
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=202611171523.oW7KTbJo-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=ismael@iodev.co.uk \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.