<?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 Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>b4cc4430 - drivers: base: Add basic devm tests for platform devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Makefile#b4cc4430</link>
        <description>drivers: base: Add basic devm tests for platform devicesPlatform devices show some inconsistencies with how devm resources arereleased when the device has been probed and when it hasn&apos;t.In particular, we can register device-managed actions no matter if thedevice has be bound to a driver or not, but devres_release_all() willonly be called if it was bound to a driver or if there&apos;s no referenceheld to it anymore.If it wasn&apos;t bound to a driver and we still have a reference,devres_release_all() will never get called. This is surprisingconsidering that if the driver isn&apos;t bound but doesn&apos;t have anyreference to it anymore, that function will get called, and if it wasbound to a driver but still has references, that function will getcalled as well.Even if that case is fairly unusual, it can easily lead to memory leaks.The plan is, with the next patch, to make it consistent and enforce thatdevres_release_all() is called no matter what situation we&apos;re in. Fornow, it just tests for the current behaviour and skips over theinconsistencies.Reviewed-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Maxime Ripard &lt;mripard@kernel.org&gt;Link: https://lore.kernel.org/r/20230720-kunit-devm-inconsistencies-test-v3-2-6aa7e074f373@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Makefile</description>
        <pubDate>Thu, 20 Jul 2023 12:45:08 +0000</pubDate>
        <dc:creator>Maxime Ripard &lt;mripard@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>06188bc8 - drivers: base: Add basic devm tests for root devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Makefile#06188bc8</link>
        <description>drivers: base: Add basic devm tests for root devicesThe root devices show some odd behaviours compared to regular &quot;bus&quot; devicesthat have been probed through the usual mechanism, so let&apos;s create kunittests to exercise those paths and odd cases.It&apos;s not clear whether root devices are even allowed to use devicemanaged resources, but the fact that it works in some cases but notothers like shown in that test suite shouldn&apos;t happen either way: wewant to make it consistent and documented.These tests will (after the following patches) ensure that consistencyand effectively document that it&apos;s allowed.If it ever turns out to be a bad idea, we can always roll back andmodify the tests then.Reviewed-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Maxime Ripard &lt;mripard@kernel.org&gt;Link: https://lore.kernel.org/r/20230720-kunit-devm-inconsistencies-test-v3-1-6aa7e074f373@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Makefile</description>
        <pubDate>Thu, 20 Jul 2023 12:45:07 +0000</pubDate>
        <dc:creator>Maxime Ripard &lt;mripard@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>6a1e2d93 - device property: build kunit tests without structleak plugin</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Makefile#6a1e2d93</link>
        <description>device property: build kunit tests without structleak pluginThe structleak plugin causes the stack frame size to grow immensely whenused with KUnit:../drivers/base/test/property-entry-test.c:492:1: warning: the frame size of 2832 bytes is larger than 2048 bytes [-Wframe-larger-than=]../drivers/base/test/property-entry-test.c:322:1: warning: the frame size of 2080 bytes is larger than 2048 bytes [-Wframe-larger-than=]../drivers/base/test/property-entry-test.c:250:1: warning: the frame size of 4976 bytes is larger than 2048 bytes [-Wframe-larger-than=]../drivers/base/test/property-entry-test.c:115:1: warning: the frame size of 3280 bytes is larger than 2048 bytes [-Wframe-larger-than=]Turn it off in this file.Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Suggested-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Makefile</description>
        <pubDate>Wed, 29 Sep 2021 21:27:11 +0000</pubDate>
        <dc:creator>Brendan Higgins &lt;brendanhiggins@google.com&gt;</dc:creator>
    </item>
<item>
        <title>586c4028 - kunit: software node: adhear to KUNIT formatting standard</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Makefile#586c4028</link>
        <description>kunit: software node: adhear to KUNIT formatting standardChange CONFIG_KUNIT_DRIVER_PE_TEST to CONFIG_DRIVER_PE_KUNIT_TEST inorderto adhear to the KUNIT *_KUNIT_TEST config name format.Fixes: aa811e3cecec (software node: introduce CONFIG_KUNIT_DRIVER_PE_TEST)Signed-off-by: Nico Pache &lt;npache@redhat.com&gt;Link: https://lore.kernel.org/r/ef06f65f4a622cf83cce5ba2ba5a060d2aa2e1b9.1618388989.git.npache@redhat.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Makefile</description>
        <pubDate>Wed, 14 Apr 2021 08:58:05 +0000</pubDate>
        <dc:creator>Nico Pache &lt;npache@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>38009c76 - drivers/base: build kunit tests without structleak plugin</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Makefile#38009c76</link>
        <description>drivers/base: build kunit tests without structleak pluginThe structleak plugin causes the stack frame size to grow immensely:drivers/base/test/property-entry-test.c: In function &apos;pe_test_reference&apos;:drivers/base/test/property-entry-test.c:481:1: error: the frame size of 2640 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]  481 | }      | ^drivers/base/test/property-entry-test.c: In function &apos;pe_test_uints&apos;:drivers/base/test/property-entry-test.c:99:1: error: the frame size of 2592 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]Turn it off in this file.Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://lore.kernel.org/r/20210125124533.101339-3-arnd@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Makefile</description>
        <pubDate>Mon, 25 Jan 2021 12:45:27 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>aa811e3c - software node: introduce CONFIG_KUNIT_DRIVER_PE_TEST</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Makefile#aa811e3c</link>
        <description>software node: introduce CONFIG_KUNIT_DRIVER_PE_TESTCurrently the property entry kunit tests are built if CONFIG_KUNIT=y.This will cause warnings when merged with the kunit tree that nowsupports tristate CONFIG_KUNIT.  While the tests appear to compileas a module, we get a warning about missing module license.It&apos;s better to have a per-test suite CONFIG variable so thatwe can do selective building of kunit-based suites, and canalso avoid merge issues like this.Fixes: c032ace71c29 (&quot;software node: add basic tests for property entries&quot;)Reported-by: Stephen Rothwell &lt;sfr@canb.auug.org.au&gt;Reported-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Signed-off-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/base/test/Makefile</description>
        <pubDate>Tue, 14 Jan 2020 16:09:43 +0000</pubDate>
        <dc:creator>Alan Maguire &lt;alan.maguire@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>c032ace7 - software node: add basic tests for property entries</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Makefile#c032ace7</link>
        <description>software node: add basic tests for property entriesThis adds tests for creating software nodes with properties supplied byPROPERTY_ENTRY_XXX() macros and fetching and validating data from saidnodes/properties.We are using KUnit framework for the tests.Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/base/test/Makefile</description>
        <pubDate>Wed, 04 Dec 2019 18:53:15 +0000</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>47bcc18c - drivers: base: test: add proper SPDX identifier to Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Makefile#47bcc18c</link>
        <description>drivers: base: test: add proper SPDX identifier to MakefileThe Makefile in the drivers/base/test/ directory did not have a SPDXidentifier on it, so fix that up.Cc: &quot;Rafael J. Wysocki&quot; &lt;rafael@kernel.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Makefile</description>
        <pubDate>Tue, 02 Apr 2019 13:32:03 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>79543cf2 - driver-core: add test module for asynchronous probing</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Makefile#79543cf2</link>
        <description>driver-core: add test module for asynchronous probingThis test module tries to test asynchronous driver probing by having adriver that sleeps for an extended period of time (5 secs) in itsprobe() method. It measures the time needed to register this driver(with device already registered) and a new device (with driver alreadyregistered). The module will fail to load if the time spent in registercall is more than half the probing sleep time.As a sanity check the driver will then try to synchronously registerdriver and device and fail if registration takes less than half of theprobing sleep time.Signed-off-by: Dmitry Torokhov &lt;dtor@chromium.org&gt;Reviewed-by: Olof Johansson &lt;olofj@chromium.org&gt;Signed-off-by: Guenter Roeck &lt;groeck@chromium.org&gt;Signed-off-by: Thierry Escande &lt;thierry.escande@collabora.com&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Makefile</description>
        <pubDate>Thu, 29 Sep 2016 15:13:14 +0000</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dtor@chromium.org&gt;</dc:creator>
    </item>
</channel>
</rss>
