From e41c2321af4cc594e747e1cc4bf775926ba88838 Mon Sep 17 00:00:00 2001 From: Bartosz Golaszewski Date: Mon, 8 May 2017 16:36:53 +0200 Subject: [PATCH] tests: fix a dmesg error message from gpio-mockup When checking if we can load gpio-mockup, we don't pass the gpio_mockup_ranges argument to the module. This makes probe() fail and causes an error message to be emitted. Pass a correct argument to gpio-mockup so that a dummy GPIO chip gets created and no errors are displayed. Signed-off-by: Bartosz Golaszewski --- tests/unit/gpiod-unit.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tests/unit/gpiod-unit.c b/tests/unit/gpiod-unit.c index f6a0b2a..100e8ca 100644 --- a/tests/unit/gpiod-unit.c +++ b/tests/unit/gpiod-unit.c @@ -357,7 +357,8 @@ static void check_gpio_mockup(void) /* Then see if we can freely load and unload it. */ status = kmod_module_probe_insert_module(globals.module, 0, - NULL, NULL, NULL, NULL); + "gpio_mockup_ranges=-1,4", + NULL, NULL, NULL); if (status) die_perr("unable to load gpio-mockup"); -- 2.30.2