From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] vfio: Allow untainted use of driver_override
Date: Fri, 20 Nov 2026 03:08:28 +0800 [thread overview]
Message-ID: <202611200233.KNmMbpyn-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "too many reports for this commit"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20261118235645.2907908-2-alex@shazbot.org>
References: <20261118235645.2907908-2-alex@shazbot.org>
TO: Alex Williamson <alex@shazbot.org>
TO: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
CC: Alex Williamson <alex@shazbot.org>
CC: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
CC: Jonathan Corbet <corbet@lwn.net>
CC: Shuah Khan <skhan@linuxfoundation.org>
CC: Randy Dunlap <rdunlap@infradead.org>
CC: "Rafael J . Wysocki" <rafael@kernel.org>
CC: Danilo Krummrich <dakr@kernel.org>
CC: Johan Hovold <johan@kernel.org>
CC: Steven Rostedt <rostedt@goodmis.org>
CC: Masami Hiramatsu <mhiramat@kernel.org>
CC: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
CC: David Lechner <dlechner@baylibre.com>
CC: Armin Wolf <W_Armin@gmx.de>
CC: Thierry Reding <thierry.reding@kernel.org>
CC: Mike Rapoport <rppt@kernel.org>
CC: Arnd Bergmann <arnd@arndb.de>
CC: Karl Mehltretter <kmehltretter@gmail.com>
CC: "Paul E . McKenney" <paulmck@kernel.org>
CC: Borislav Petkov <bp@alien8.de>
CC: Dapeng Mi <dapeng1.mi@linux.intel.com>
CC: Marco Elver <elver@google.com>
CC: "Ethan Nelson-Moore" <enelsonmoore@gmail.com>
CC: Jeff Layton <jlayton@kernel.org>
CC: Bradley Morgan <brads@mainlining.org>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
CC: Petr Mladek <pmladek@suse.com>
CC: Pnina Feder <pnina.feder@mobileye.com>
CC: Mete Durlu <meted@linux.ibm.com>
Hi Alex,
kernel test robot noticed the following build errors:
[auto build test ERROR on awilliam-vfio/next]
[also build test ERROR on linus/master v7.4-rc3 next-20261116]
[cannot apply to awilliam-vfio/for-linus]
[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/Alex-Williamson/vfio-Allow-untainted-use-of-driver_override/20261118-165644
base: https://github.com/awilliam/linux-vfio.git next
patch link: https://lore.kernel.org/r/20261118235645.2907908-2-alex%40shazbot.org
patch subject: [PATCH] vfio: Allow untainted use of driver_override
:::::: branch date: 9 hours ago
:::::: commit date: 9 hours ago
config: s390-randconfig-1001-20261119 (https://download.01.org/0day-ci/archive/20261120/202611200233.KNmMbpyn-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 14.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261120/202611200233.KNmMbpyn-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/r/202611200233.KNmMbpyn-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/vfio/platform/vfio_amba.c:140:18: error: 'struct device_driver' has no member named 'support_driver_override'
140 | .support_driver_override = true,
| ^~~~~~~~~~~~~~~~~~~~~~~
>> drivers/vfio/platform/vfio_amba.c:140:44: error: initialization of 'const struct bus_type *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
140 | .support_driver_override = true,
| ^~~~
drivers/vfio/platform/vfio_amba.c:140:44: note: (near initialization for 'vfio_amba_driver.drv.bus')
vim +140 drivers/vfio/platform/vfio_amba.c
36fe431f2811fa3 Antonios Motakis 2015-03-16 133
36fe431f2811fa3 Antonios Motakis 2015-03-16 134 static struct amba_driver vfio_amba_driver = {
36fe431f2811fa3 Antonios Motakis 2015-03-16 135 .probe = vfio_amba_probe,
36fe431f2811fa3 Antonios Motakis 2015-03-16 136 .remove = vfio_amba_remove,
ec29d22caea85d9 Geert Uytterhoeven 2024-02-26 137 .id_table = vfio_amba_ids,
36fe431f2811fa3 Antonios Motakis 2015-03-16 138 .drv = {
36fe431f2811fa3 Antonios Motakis 2015-03-16 139 .name = "vfio-amba",
722a3b248ee2110 Alex Williamson 2026-11-18 @140 .support_driver_override = true,
36fe431f2811fa3 Antonios Motakis 2015-03-16 141 },
70693f470848f05 Lu Baolu 2022-04-18 142 .driver_managed_dma = true,
36fe431f2811fa3 Antonios Motakis 2015-03-16 143 };
36fe431f2811fa3 Antonios Motakis 2015-03-16 144
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-11-19 19:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 19:08 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-19 20:00 [PATCH] vfio: Allow untainted use of driver_override kernel test robot
2026-11-19 16:53 kernel test robot
2026-11-18 16:22 [PATCH] driver core: Disable driver overriding by default Danilo Krummrich
2026-11-18 23:56 ` [PATCH] vfio: Allow untainted use of driver_override Alex Williamson
2026-11-19 0:09 ` sashiko-bot
2026-11-19 0:12 ` Creeley, Brett
2026-11-19 14:56 ` Mostafa Saleh
2026-11-19 16:51 ` kernel test robot
2026-11-19 16:51 ` kernel test robot
2026-11-19 17:40 ` kernel test robot
2026-11-19 18:36 ` Ankit Agrawal
2026-11-20 2:17 ` Yao Yuan
2026-11-20 14:10 ` Uwe Kleine-König
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=202611200233.KNmMbpyn-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.