<?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 Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>55b7aee9 - drivers: base: test: Enable device model tests with KUNIT_ALL_TESTS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Kconfig#55b7aee9</link>
        <description>drivers: base: test: Enable device model tests with KUNIT_ALL_TESTSPer commit bebe94b53eb7 (&quot;drivers: base: default KUNIT_* fragments toKUNIT_ALL_TESTS&quot;), it seems like we should default to KUNIT_ALL_TESTS.This enables these platform_device tests for common configurations, suchas with:  ./tools/testing/kunit/kunit.py runSigned-off-by: Brian Norris &lt;briannorris@chromium.org&gt;Reviewed-by: David Gow &lt;davidgow@google.com&gt;Reviewed-by: Maxime Ripard &lt;mripard@kernel.org&gt;Reviewed-by: Rob Herring (Arm) &lt;robh@kernel.org&gt;Link: https://lore.kernel.org/r/20241216201148.535115-3-briannorris@chromium.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Kconfig</description>
        <pubDate>Mon, 16 Dec 2024 20:11:43 +0000</pubDate>
        <dc:creator>Brian Norris &lt;briannorris@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>98ad1dd0 - drivers: base: test: Make property entry API test modular</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Kconfig#98ad1dd0</link>
        <description>drivers: base: test: Make property entry API test modularThere is no reason why the KUnit Tests for the property entry API canonly be built-in.  Add support for building these tests as a loadablemodule, like is supported by most other tests.Signed-off-by: Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;Link: https://lore.kernel.org/r/98388154383df9d4ced73946efd18318aeea50e2.1695820382.git.geert+renesas@glider.beSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Kconfig</description>
        <pubDate>Wed, 27 Sep 2023 13:20:10 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert+renesas@glider.be&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/Kconfig#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/Kconfig</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>9dc5f12f - device property: Add a blank line in Kconfig of tests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Kconfig#9dc5f12f</link>
        <description>device property: Add a blank line in Kconfig of testsSeems the blank line to separate entries in Kconfig was missing.Add it.Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;Acked-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Link: https://lore.kernel.org/r/20221122133600.49897-4-andriy.shevchenko@linux.intel.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Kconfig</description>
        <pubDate>Tue, 22 Nov 2022 13:36:00 +0000</pubDate>
        <dc:creator>Andy Shevchenko &lt;andriy.shevchenko@linux.intel.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/Kconfig#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/Kconfig</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>bebe94b5 - drivers: base: default KUNIT_* fragments to KUNIT_ALL_TESTS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Kconfig#bebe94b5</link>
        <description>drivers: base: default KUNIT_* fragments to KUNIT_ALL_TESTSThis makes it easier to enable all KUnit fragments.Adding &apos;if !KUNIT_ALL_TESTS&apos; so individual tests can not be turned off.Therefore if KUNIT_ALL_TESTS is enabled that will hide the prompt inmenuconfig.Reviewed-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Anders Roxell &lt;anders.roxell@linaro.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Kconfig</description>
        <pubDate>Mon, 11 May 2020 13:14:33 +0000</pubDate>
        <dc:creator>Anders Roxell &lt;anders.roxell@linaro.org&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/Kconfig#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/Kconfig</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>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/test/Kconfig#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/test/Kconfig</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +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/Kconfig#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/Kconfig</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>
