From: Shuah Khan <skhan@linuxfoundation•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
David Gow <davidgow@google•com>,
Marie Zhussupova <marievic@google•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
KUnit Development <kunit-dev@googlegroups•com>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Shuah Khan <skhan@linuxfoundation•org>
Subject: Re: linux-next: build failure after merge of the kunit-next tree
Date: Mon, 18 Aug 2025 10:32:41 -0600 [thread overview]
Message-ID: <1befd7ab-f343-450f-9484-0cef21fe2da8@linuxfoundation.org> (raw)
In-Reply-To: <20250818120846.347d64b1@canb.auug.org.au>
On 8/17/25 20:08, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kunit-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
Thank you Stephen. I did a allmodconfig build on 6.17-rc1 base - didn't
see the error.
Marie, David, can you take a look this. Looks like conflict with drm
in next?
>
> In file included from include/kunit/static_stub.h:18,
> from drivers/gpu/drm/xe/xe_bo.c:20:
> drivers/gpu/drm/xe/tests/xe_bo.c:610:48: error: initialization of 'const void * (*)(struct kunit *, const void *, char *)' from incompatible pointer type 'const void * (*)(const void *, char *)' [-Wincompatible-pointer-types]
> 610 | KUNIT_CASE_PARAM(xe_ccs_migrate_kunit, xe_pci_live_device_gen_param),
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> include/kunit/test.h:210:38: note: in definition of macro 'KUNIT_CASE_PARAM'
> 210 | .generate_params = gen_params, .module_name = KBUILD_MODNAME}
> | ^~~~~~~~~~
> drivers/gpu/drm/xe/tests/xe_bo.c:610:48: note: (near initialization for 'xe_bo_tests[0].generate_params')
> 610 | KUNIT_CASE_PARAM(xe_ccs_migrate_kunit, xe_pci_live_device_gen_param),
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> include/kunit/test.h:210:38: note: in definition of macro 'KUNIT_CASE_PARAM'
> 210 | .generate_params = gen_params, .module_name = KBUILD_MODNAME}
> | ^~~~~~~~~~
> drivers/gpu/drm/xe/tests/xe_bo.c:611:45: error: initialization of 'const void * (*)(struct kunit *, const void *, char *)' from incompatible pointer type 'const void * (*)(const void *, char *)' [-Wincompatible-pointer-types]
> 611 | KUNIT_CASE_PARAM(xe_bo_evict_kunit, xe_pci_live_device_gen_param),
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> include/kunit/test.h:210:38: note: in definition of macro 'KUNIT_CASE_PARAM'
> 210 | .generate_params = gen_params, .module_name = KBUILD_MODNAME}
> | ^~~~~~~~~~
> drivers/gpu/drm/xe/tests/xe_bo.c:611:45: note: (near initialization for 'xe_bo_tests[1].generate_params')
> 611 | KUNIT_CASE_PARAM(xe_bo_evict_kunit, xe_pci_live_device_gen_param),
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> include/kunit/test.h:210:38: note: in definition of macro 'KUNIT_CASE_PARAM'
> 210 | .generate_params = gen_params, .module_name = KBUILD_MODNAME}
> | ^~~~~~~~~~
> drivers/gpu/drm/xe/tests/xe_bo.c:624:51: error: initialization of 'const void * (*)(struct kunit *, const void *, char *)' from incompatible pointer type 'const void * (*)(const void *, char *)' [-Wincompatible-pointer-types]
> 624 | KUNIT_CASE_PARAM_ATTR(xe_bo_shrink_kunit, xe_pci_live_device_gen_param,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> include/kunit/test.h:223:38: note: in definition of macro 'KUNIT_CASE_PARAM_ATTR'
> 223 | .generate_params = gen_params, \
> | ^~~~~~~~~~
> drivers/gpu/drm/xe/tests/xe_bo.c:624:51: note: (near initialization for 'xe_bo_shrink_test[0].generate_params')
> 624 | KUNIT_CASE_PARAM_ATTR(xe_bo_shrink_kunit, xe_pci_live_device_gen_param,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> include/kunit/test.h:223:38: note: in definition of macro 'KUNIT_CASE_PARAM_ATTR'
> 223 | .generate_params = gen_params, \
> | ^~~~~~~~~~
>
> Caused by commit
>
> 444be9072fca ("kunit: Pass parameterized test context to generate_params()")
>
> I have used the kunit-next tree from next-20250815 for today.
>
thanks,
-- Shuah
next prev parent reply other threads:[~2025-08-18 16:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 2:08 linux-next: build failure after merge of the kunit-next tree Stephen Rothwell
2025-08-18 16:32 ` Shuah Khan [this message]
2025-08-19 7:44 ` David Gow
2025-08-25 6:05 ` Stephen Rothwell
2025-08-26 2:15 ` Shuah Khan
2025-08-26 9:24 ` David Gow
2025-08-27 5:49 ` Shuah Khan
2025-08-27 6:37 ` David Gow
-- strict thread matches above, loose matches on Subject: below --
2024-10-04 4:11 Stephen Rothwell
2024-10-04 13:26 ` Gabriela Bittencourt
2024-10-04 18:36 ` Shuah Khan
2024-02-29 4:26 Stephen Rothwell
2024-02-29 15:07 ` Shuah Khan
2024-03-01 7:15 ` David Gow
2024-03-01 10:43 ` Stephen Rothwell
2024-03-01 16:05 ` Shuah Khan
2024-03-01 20:46 ` Stephen Rothwell
2024-03-01 22:30 ` Shuah Khan
2024-03-06 15:25 ` Shuah Khan
2024-02-28 2:48 Stephen Rothwell
2024-02-28 3:26 ` Shuah Khan
2020-01-16 5:57 Stephen Rothwell
2020-01-16 11:23 ` Alan Maguire
2020-01-16 23:27 ` Rafael J. Wysocki
2020-01-10 6:43 Stephen Rothwell
2020-01-10 11:56 ` Alan Maguire
2020-01-13 21:11 ` Brendan Higgins
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=1befd7ab-f343-450f-9484-0cef21fe2da8@linuxfoundation.org \
--to=skhan@linuxfoundation$(echo .)org \
--cc=davidgow@google$(echo .)com \
--cc=kunit-dev@googlegroups$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marievic@google$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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