[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180218193849.GA29324@ravnborg.org>
Date: Sun, 18 Feb 2018 20:38:49 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: linux-kbuild@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Nicolas Pitre <nicolas.pitre@...aro.org>,
"Luis R . Rodriguez" <mcgrof@...e.com>,
Randy Dunlap <rdunlap@...radead.org>,
Ulf Magnusson <ulfalizer@...il.com>,
Michal Marek <michal.lkml@...kovi.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
Tony Luck <tony.luck@...el.com>, Borislav Petkov <bp@...e.de>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Heinrich Schuchardt <xypron.glpk@....de>,
Yaakov Selkowitz <yselkowi@...hat.com>,
linux-ia64@...r.kernel.org, Fenghua Yu <fenghua.yu@...el.com>,
Marc Herbert <marc.herbert@...el.com>
Subject: Re: [PATCH 00/14] Add Kconfig unit tests
Hi Masahiro.
On Tue, Feb 06, 2018 at 09:34:40AM +0900, Masahiro Yamada wrote:
> I am applying various patches to Kconfig these days.
>
> However, I fear regressions. I have been thinking of unit-tests.
>
> There are various cryptic parts in Kconfig and corner cases where
> it is difficult to notice breakage. If unit-tests cover those,
> I will be able to apply changes more confidently.
>
> So, here is the trial.
...
Great to see this done.
And +1 for basing this on a standard framework rather than inventing your own.
> If you have an idea for better implementation, comments are appreciated.
Nope, please continue with pytest.
Sam
Powered by blists - more mailing lists