<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in .kunitconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>9854781d - kunit: tool: make --kunitconfig accept dirs, add lib/kunit fragment</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/.kunitconfig#9854781d</link>
        <description>kunit: tool: make --kunitconfig accept dirs, add lib/kunit fragmentTL;DR$ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunitPer suggestion from Ted [1], we can reduce the amount of typing byassuming a convention that these files are named &apos;.kunitconfig&apos;.In the case of [1], we now have$ ./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4Also add in such a fragment for kunit itself so we can give that as anexample more close to home (and thus less likely to be accidentallybroken).[1] https://lore.kernel.org/linux-ext4/YCNF4yP1dB97zzwD@mit.edu/Signed-off-by: Daniel Latypov &lt;dlatypov@google.com&gt;Reviewed-by: David Gow &lt;davidgow@google.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/.kunitconfig</description>
        <pubDate>Mon, 22 Feb 2021 22:52:41 +0000</pubDate>
        <dc:creator>Daniel Latypov &lt;dlatypov@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
