<?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>5e8c5299 - kconfig: report recursive dependency involving &apos;imply&apos;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/kconfig/tests/err_recursive_dep/Kconfig#5e8c5299</link>
        <description>kconfig: report recursive dependency involving &apos;imply&apos;Currently, Kconfig does not complain about the recursive dependencywhere &apos;imply&apos; keywords are involved.[Test Code]  config A          bool &quot;a&quot;  config B          bool &quot;b&quot;          imply A          depends on AIn the code above, Kconfig cannot calculate the symbol values correctlydue to the circular dependency.  For example, allyesconfig followed bysyncconfig results in an odd behavior because CONFIG_B becomes visiblein syncconfig.  $ make allyesconfig  scripts/kconfig/conf  --allyesconfig Kconfig  #  # configuration written to .config  #  $ cat .config  #  # Automatically generated file; DO NOT EDIT.  # Main menu  #  CONFIG_A=y  $ make syncconfig  scripts/kconfig/conf  --syncconfig Kconfig  *  * Restart config...  *  *  * Main menu  *  a (A) [Y/n/?] y    b (B) [N/y/?] (NEW)To detect this correctly, sym_check_expr_deps() should recurse tonot only sym-&gt;rev_dep.expr but also sym-&gt;implied.expr .At this moment, sym_check_print_recursive() cannot distinguish&apos;select&apos; and &apos;imply&apos; since it does not know the precise contextwhere the recursive dependency has been hit.  This will be solvedby the next commit.In fact, even the document and the unit-test are confused.  Using&apos;imply&apos; does not solve recursive dependency since &apos;imply&apos; addressesthe unmet direct dependency, which &apos;select&apos; could cause.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Tested-by: Dirk Gouders &lt;dirk@gouders.net&gt;

            List of files:
            /linux-6.15/scripts/kconfig/tests/err_recursive_dep/Kconfig</description>
        <pubDate>Wed, 15 Aug 2018 05:59:44 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>f1575595 - kconfig: error out when seeing recursive dependency</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/kconfig/tests/err_recursive_dep/Kconfig#f1575595</link>
        <description>kconfig: error out when seeing recursive dependencyOriginally, recursive dependency was a fatal error for Kconfigbecause Kconfig cannot compute symbol values in such a situation.Commit d595cea62403 (&quot;kconfig: print more info when we see a recursivedependency&quot;) changed it to a warning, which I guess was not intentional.Get it back to an error again.Also, rename the unit test directory &quot;warn_recursive_dep&quot; to&quot;err_recursive_dep&quot; so that it matches to the behavior.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Tested-by: Dirk Gouders &lt;dirk@gouders.net&gt;

            List of files:
            /linux-6.15/scripts/kconfig/tests/err_recursive_dep/Kconfig</description>
        <pubDate>Wed, 15 Aug 2018 05:59:43 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
</channel>
</rss>
