[PATCH v2] selftests: timers: clocksource-switch: Adapt progress to kselftest framework

Signed-off-by: Geert Uytterhoeven Reviewed-by: Thomas Gleixner --- v2: - Add Reviewed-by. --- tools/testing/selftests/timers/clocksource-switch.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/testing/selftests/timers/clocksource-switch.c b/tools/testing/selfte

Re: [PATCH net-next v10 2/3] net: gro: move L3 flush checks to tcp_gro_receive and udp_gro_receive_segment

ly you just want to make this explicit, by adding u16 pad; here. > > + /* used to support CHECKSUM_COMPLETE for tunneling protocols */ > + __wsum csum; Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds

Re: [PATCH 00/14] Add support for suppressing warning backtraces

nction names in BUG/WARNING messages). That change, if > desired, can be made later. Unfortunately this also increases kernel size in the CONFIG_KUNIT=m case (ca. 80 KiB for atari_defconfig), making it less attractive to have kunit and all tests enabled as modules in my standard kernel. Gr{oetje,ee

Re: [PATCH 11/14] s390: Add support for suppressing warning backtraces

_), \ > + : : "i" (__BUG_FUNC), \ > + "i" (__LINE__), \ > "i" (x),

Re: [PATCH 2/7] of: Create of_root if no dtb provided by firmware

On Tue, Mar 12, 2024 at 3:41 PM Geert Uytterhoeven wrote: > On Wed, Feb 21, 2024 at 3:06 PM Rob Herring wrote: > > On Fri, Feb 16, 2024 at 11:08 PM Saurabh Singh Sengar > > wrote: > > > This adds the strict check for compatible which makes compatible > > > to be

Re: [PATCH 2/7] of: Create of_root if no dtb provided by firmware

* enabling full constraints and since it's much more natural * with DT to provide them just assume that a DT enabled * system has full constraints. */ if (of_have_populated_dt()) has_full_constraints = true; ... }

Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

Hi Maxime, On Mon, Mar 4, 2024 at 11:20 AM Maxime Ripard wrote: > On Mon, Mar 04, 2024 at 11:07:22AM +0100, Geert Uytterhoeven wrote: > > On Mon, Mar 4, 2024 at 10:15 AM Maxime Ripard wrote: > > > On Mon, Mar 04, 2024 at 09:12:38AM +0100, Geert Uytterhoeven wrote: > >

Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

Hi Maxime, On Mon, Mar 4, 2024 at 10:15 AM Maxime Ripard wrote: > On Mon, Mar 04, 2024 at 09:12:38AM +0100, Geert Uytterhoeven wrote: > > On Sun, Mar 3, 2024 at 10:30 AM Geert Uytterhoeven > > wrote: > > > On Sun, Mar 3, 2024 at 3:30 AM Randy Dunlap wrote: > >

Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

On Sun, Mar 3, 2024 at 10:30 AM Geert Uytterhoeven wrote: > On Sun, Mar 3, 2024 at 3:30 AM Randy Dunlap wrote: > > On 3/2/24 14:10, Guenter Roeck wrote: > > > While checkpatch is indeed of arguable value, I think it would help a > > > lot not having to bother a

Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

mail when builds get broken, and when they get fixed again. I receive such emails for the m68k builds. I have the feeling this is not used up to its full potential yet. My initial plan with the "Build regressions/improvements in ..." emails [1] was to fully automate this, and enabl

Re: [PATCH v10] lib: checksum: Use aligned accesses for ip_fast_csum and csum_ipv6_magic tests

the point of writing tests for a core functionality like network checksumming that do not match the expected functionality? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org In pers

Re: [PATCH v2 01/31] ntsync: Introduce the ntsync driver and character device.

be called ntsync. > + > + If unsure, say N. Is it useful to have this feature on systems or architectures that are not supported by Windows NT? If not, this should depend on || COMPILE_TEST. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linu

[PATCH resend] selftests: timers: clocksource-switch: Adapt progress to kselftest framework

Signed-off-by: Geert Uytterhoeven --- When just running the test, the output looks like: # Validating clocksource arch_sys_counter TAP version 13 1..12 ok 1 CLOCK_REALTIME ... # Validating clocksource ffca.timer TAP version 13 1..12 ok 1 CLOCK_REALTIME

Re: [PATCH v3 7/7] of: Add KUnit test to confirm DTB is loaded

it doesn't call the > unflatten_(and_copy)?_device_tree() function, so we don't populate a > root node on that architecture. One solution would be to make CONFIG_OF > unavailable on m68k. Or we have to make sure DT works on any > architecture. Rob, what do you prefer here? I guess the

Re: [PATCH v4] kunit: run test suites only after module initialization completes

start address is checked > v2: > - add include > > Fixes: 2810c1e99867 ("kunit: Fix wild-memory-access bug in > kunit_free_suite_set()") > Reviewed-by: David Gow > Tested-by: Rae Moar > Tested-by: Richard Fitzgerald > Reviewed-by: Javier Martinez Canillas &

Re: [PATCH 1/6] arm64: Unconditionally call unflatten_device_tree()

we can run DT tests for the clk > framework; why can't that just depend on the system being booted with DT > rather > than ACPI? We have other tests which are architecture and/or configuration > dependent... There is definitely a merit in running (platform-independent) DT tests on any platform,

Re: [PATCH 1/6] arm64: Unconditionally call unflatten_device_tree()

Hi Mark, On Thu, Jan 18, 2024 at 4:23 PM Mark Rutland wrote: > On Tue, Jan 16, 2024 at 03:13:42PM +0100, Geert Uytterhoeven wrote: > > On Tue, Jan 16, 2024 at 12:51 PM Mark Rutland wrote: > > > On Fri, Jan 12, 2024 at 12:07:44PM -0800, Stephen Boyd wrote: > >

Re: [PATCH 4/6] of: Create of_root if no dtb provided by firmware

estrict the root node to new nodes only and no new > or changed properties. Changing (or appending to) the root "compatible" and/or "model" properties is useful in case of large extension boards, though. This is also the case for DTBs created from a base DTB

Re: [PATCH 1/6] arm64: Unconditionally call unflatten_device_tree()

ition, we don't want people being > "clever" and describing disparate portions of their system in ACPI and DT. We'd get to the latter anyway, when plugging in a USB device where the circuitry on/behind the USB device is described in DT. Gr{oetje,eeting}s, Geert -

Re: [RFC PATCH v5 1/4] mseal: Wire up mseal syscall

ntime, 457 and 458 are already taken by statmount() and listmount(): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/m68k/kernel/syscalls/syscall.tbl#n459 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux

[PATCH] selftests: timers: clocksource-switch: Adapt progress to kselftest framework

Signed-off-by: Geert Uytterhoeven --- When just running the test, the output looks like: # Validating clocksource arch_sys_counter TAP version 13 1..12 ok 1 CLOCK_REALTIME ... # Validating clocksource ffca.timer TAP version 13 1..12 ok 1 CLOCK_REALTIME

Re: [RFC PATCH v2 04/10] docs: submitting-patches: Introduce Tested-with:

h haven't? I expect reviewers/maintainers to scrutinize (extra) patches that lack such a tag (or lack the same under the "---"), and/or run the test suite theirselves. I.e. does this serve any purpose _after_ the patch has been applied? Gr{oetje,eeting}s, Geert

Re: [PATCH 1/3] MAINTAINERS: Introduce V: field for required tests

xes > as seen on drivers/staging/)? After having seen the introduction of too many build failures, I'm inclined to ask for an even stronger proof of testing for "trivial" fixes for drivers/staging... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There

[PATCH] drivers: base: test: Make property entry API test modular

There is no reason why the KUnit Tests for the property entry API can only be built-in. Add support for building these tests as a loadable module, like is supported by most other tests. Signed-off-by: Geert Uytterhoeven --- drivers/base/test/Kconfig | 4 ++-- drivers/base/test