mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Gow <david@davidgow.net>
To: Mark Brown <broonie@kernel.org>,
	Brendan Higgins <brendan.higgins@linux.dev>,
	Rae Moar <raemoar63@gmail.com>
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kunit: configs: Enable gpiolib for all_tests.config
Date: Thu, 16 Jul 2026 14:30:59 +0800	[thread overview]
Message-ID: <a4ce393d-3d81-40ca-b0c5-28b6ea36cfe8@davidgow.net> (raw)
In-Reply-To: <20260715-kunit-gpiolib-v1-1-d2824313e1db@kernel.org>

Le 16/07/2026 à 4:15 AM, Mark Brown a écrit :
> Some of the Cirrus driver tests require gpiolib, enable it in the all
> tests configuration.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---

Thanks, Mark.

We've already accepted Bart's equivalent patch here:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/commit/?h=kunit&id=34b5c0132952c3d176bf5a169c8f7093ecb8c4e8

Cheers,
-- David

>  tools/testing/kunit/configs/all_tests.config | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/tools/testing/kunit/configs/all_tests.config b/tools/testing/kunit/configs/all_tests.config
> index bccc2c77196d..350171ed655d 100644
> --- a/tools/testing/kunit/configs/all_tests.config
> +++ b/tools/testing/kunit/configs/all_tests.config
> @@ -59,3 +59,5 @@ CONFIG_SND=y
>  CONFIG_SND_SOC=y
>  CONFIG_SND_SOC_TOPOLOGY_BUILD=y
>  CONFIG_SND_SOC_CS35L56_I2C=y
> +
> +CONFIG_GPIOLIB=y
> 
> ---
> base-commit: a13c140cc289c0b7b3770bce5b3ad42ab35074aa
> change-id: 20260715-kunit-gpiolib-b0921af52589
> 
> Best regards,
> --  
> Mark Brown <broonie@kernel.org>
> 


      reply	other threads:[~2026-07-16  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 20:15 Mark Brown
2026-07-16  6:30 ` David Gow [this message]

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=a4ce393d-3d81-40ca-b0c5-28b6ea36cfe8@davidgow.net \
    --to=david@davidgow.net \
    --cc=brendan.higgins@linux.dev \
    --cc=broonie@kernel.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=raemoar63@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®