<?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>11923e0d - powerpc/cell: Remove CBE_CPUFREQ_SPU_GOVERNOR</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#11923e0d</link>
        <description>powerpc/cell: Remove CBE_CPUFREQ_SPU_GOVERNORAlthough this driver is still buildable, it can&apos;t actually do anythingin practice now that the low-level cpufreq driver for Cell has beendisabled due to the removal of CBE_RAS.Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Signed-off-by: Madhavan Srinivasan &lt;maddy@linux.ibm.com&gt;Link: https://patch.msgid.link/20241218105523.416573-5-mpe@ellerman.id.au

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Wed, 18 Dec 2024 10:54:53 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&gt;</dc:creator>
    </item>
<item>
        <title>38efe5a9 - powerpc: Remove PPC_PMI and driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#38efe5a9</link>
        <description>powerpc: Remove PPC_PMI and driverCONFIG_PPC_PMI is no longer selectable now that PPC_IBM_CELL_BLADE hasbeen removed, via the dependency on PPC_IBM_CELL_POWERBUTTON.So remove it and the driver, and the pmi.h header which it was the onlyuser of.Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Signed-off-by: Madhavan Srinivasan &lt;maddy@linux.ibm.com&gt;Link: https://patch.msgid.link/20241218105523.416573-3-mpe@ellerman.id.au

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Wed, 18 Dec 2024 10:54:51 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&gt;</dc:creator>
    </item>
<item>
        <title>05bf59fb - powerpc/cell: Remove support for IBM Cell Blades</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#05bf59fb</link>
        <description>powerpc/cell: Remove support for IBM Cell BladesIBM Cell Blades used the Cell processor and the &quot;blade&quot; server formfactor. They were sold as models QS20, QS21 &amp; QS22 from roughly 2006 to2012 [1]. They were used in a few supercomputers (eg. Roadrunner) thathave since been dismantled, and were not that widely used otherwise.Until recently I still had a working QS22, which meant I was able tokeep the platform support working, but unfortunately that machine hasnow died.I&apos;m not aware of any users. If there is a user that wants to keep theupstream support working, we can look at bringing some of the code backas appropriate.See previous discussion at [2].Remove the top-level config symbol PPC_IBM_CELL_BLADE, and thenthe dependent symbols PPC_CELL_NATIVE, PPC_CELL_COMMON, CBE_RAS,PPC_IBM_CELL_RESETBUTTON, PPC_IBM_CELL_POWERBUTTON, CBE_THERM, andAXON_MSI. Then remove the associated C files and headers, and trimunused header content (some is shared with PS3).Note that PPC_CELL_COMMON sounds like it would build code shared withPS3, but it does not. It&apos;s a relic from when code was shared between theBlade support and QPACE support.Most of the primary authors already have CREDITS entries, with theexception of Christian, so add one for him.[1]: https://www.theregister.com/2011/06/28/ibm_kills_qs22_blade[2]: https://lore.kernel.org/linuxppc-dev/60581044-df82-40ad-b94c-56468007a93e@app.fastmail.comAcked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: Jeremy Kerr &lt;jk@ozlabs.org&gt;Acked-by: Segher Boessenkool &lt;segher@kernel.crashing.org&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Signed-off-by: Madhavan Srinivasan &lt;maddy@linux.ibm.com&gt;Link: https://patch.msgid.link/20241218105523.416573-1-mpe@ellerman.id.au

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Wed, 18 Dec 2024 10:54:49 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&gt;</dc:creator>
    </item>
<item>
        <title>c2857374 - powerpc/64s: Make hash MMU support configurable</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#c2857374</link>
        <description>powerpc/64s: Make hash MMU support configurableThis adds Kconfig selection which allows 64s hash MMU support to bedisabled. It can be disabled if radix support is enabled, the minimumsupported CPU type is POWER9 (or higher), and KVM is not selected.Signed-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20211201144153.2456614-17-npiggin@gmail.com

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Wed, 01 Dec 2021 14:41:51 +0000</pubDate>
        <dc:creator>Nicholas Piggin &lt;npiggin@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>7ebc4903 - powerpc: Rename PPC_NATIVE to PPC_HASH_MMU_NATIVE</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#7ebc4903</link>
        <description>powerpc: Rename PPC_NATIVE to PPC_HASH_MMU_NATIVEPPC_NATIVE now only controls the native HPT code, so rename it to bemore descriptive. Restrict it to Book3S only.Signed-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20211201144153.2456614-3-npiggin@gmail.com

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Wed, 01 Dec 2021 14:41:37 +0000</pubDate>
        <dc:creator>Nicholas Piggin &lt;npiggin@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>e37af801 - powerpc: Move the use of irq_domain_add_nomap() behind a config option</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#e37af801</link>
        <description>powerpc: Move the use of irq_domain_add_nomap() behind a config optionOnly a handful of old PPC systems are still using the old &apos;nomap&apos;variant of the irqdomain library. Move the associated definitionsbehind a configuration option, which will allow us to make somemore radical changes.Signed-off-by: Marc Zyngier &lt;maz@kernel.org&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Sun, 04 Apr 2021 12:06:39 +0000</pubDate>
        <dc:creator>Marc Zyngier &lt;maz@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>7a3c90df - arch: powerpc: Stop building and using oprofile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#7a3c90df</link>
        <description>arch: powerpc: Stop building and using oprofileThe &quot;oprofile&quot; user-space tools don&apos;t use the kernel OPROFILE supportany more, and haven&apos;t in a long time. User-space has been converted tothe perf interfaces.This commits stops building oprofile for powerpc and removes anyreference to it from directories in arch/powerpc/ apart fromarch/powerpc/oprofile, which will be removed in the next commit (this isbroken into two commits as the size of the commit became very big, ~5klines).Note that the member &quot;oprofile_cpu_type&quot; in &quot;struct cpu_spec&quot; isn&apos;tremoved as it was also used by other parts of the code.Suggested-by: Christoph Hellwig &lt;hch@infradead.org&gt;Suggested-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Signed-off-by: Viresh Kumar &lt;viresh.kumar@linaro.org&gt;Acked-by: Robert Richter &lt;rric@kernel.org&gt;Acked-by: William Cohen &lt;wcohen@redhat.com&gt;Acked-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Thu, 14 Jan 2021 11:35:23 +0000</pubDate>
        <dc:creator>Viresh Kumar &lt;viresh.kumar@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>b648a513 - powerpc/spufs: add CONFIG_COREDUMP dependency</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#b648a513</link>
        <description>powerpc/spufs: add CONFIG_COREDUMP dependencyThe kernel test robot pointed out a slightly different error messageafter recent commit 5456ffdee666 (&quot;powerpc/spufs: simplify spufs coredumping&quot;) to spufs for a configuration that never worked:   powerpc64-linux-ld: arch/powerpc/platforms/cell/spufs/file.o: in function `.spufs_proxydma_info_dump&apos;:&gt;&gt; file.c:(.text+0x4c68): undefined reference to `.dump_emit&apos;   powerpc64-linux-ld: arch/powerpc/platforms/cell/spufs/file.o: in function `.spufs_dma_info_dump&apos;:   file.c:(.text+0x4d70): undefined reference to `.dump_emit&apos;   powerpc64-linux-ld: arch/powerpc/platforms/cell/spufs/file.o: in function `.spufs_wbox_info_dump&apos;:   file.c:(.text+0x4df4): undefined reference to `.dump_emit&apos;Add a Kconfig dependency to prevent this from happening again.Reported-by: kernel test robot &lt;lkp@intel.com&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: Jeremy Kerr &lt;jk@ozlabs.org&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20200706132302.3885935-1-arnd@arndb.de

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Mon, 06 Jul 2020 13:22:46 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>eb01d42a - PCI: consolidate PCI config entry in drivers/pci</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#eb01d42a</link>
        <description>PCI: consolidate PCI config entry in drivers/pciThere is no good reason to duplicate the PCI menu in every architecture.Instead provide a selectable HAVE_PCI symbol that indicates availabilityof PCI support, and a FORCE_PCI symbol to for PCI on and the handle therest in drivers/pci.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Palmer Dabbelt &lt;palmer@sifive.com&gt;Acked-by: Max Filippov &lt;jcmvbkbc@gmail.com&gt;Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Acked-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Acked-by: Paul Burton &lt;paul.burton@mips.com&gt;Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Thu, 15 Nov 2018 19:05:32 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>719736e1 - powerpc: remove redundant &apos;default n&apos; from Kconfig-s</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#719736e1</link>
        <description>powerpc: remove redundant &apos;default n&apos; from Kconfig-s&apos;default n&apos; is the default value for any bool or tristate Kconfigsetting so there is no need to write it explicitly.Also since commit f467c5640c29 (&quot;kconfig: only write &apos;# CONFIG_FOOis not set&apos; for visible symbols&quot;) the Kconfig behavior is the sameregardless of &apos;default n&apos; being present or not:    ...    One side effect of (and the main motivation for) this change is making    the following two definitions behave exactly the same:        config FOO                bool        config FOO                bool                default n    With this change, neither of these will generate a    &apos;# CONFIG_FOO is not set&apos; line (assuming FOO isn&apos;t selected/implied).    That might make it clearer to people that a bare &apos;default n&apos; is    redundant.    ...Signed-off-by: Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Tue, 09 Oct 2018 15:39:46 +0000</pubDate>
        <dc:creator>Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.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/arch/powerpc/platforms/cell/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/arch/powerpc/platforms/cell/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>33596727 - powerpc: Make selects of IBM_EMAC_* depend on IBM_EMAC</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#33596727</link>
        <description>powerpc: Make selects of IBM_EMAC_* depend on IBM_EMACWe have a bunch of Kconfig symbols which select various IBM_EMAC_*symbols. These all cause warnings when IBM_EMAC is not selected.eg.  warning: (PPC_CELL_NATIVE &amp;&amp; BLUESTONE &amp;&amp; CANYONLANDS &amp;&amp; GLACIER &amp;&amp;  EIGER &amp;&amp; 440EPX &amp;&amp; 440GRX &amp;&amp; 440GX &amp;&amp; 460SX &amp;&amp; 405EX) selects  IBM_EMAC_RGMII which has unmet direct dependencies (NETDEVICES &amp;&amp;  ETHERNET &amp;&amp; NET_VENDOR_IBM)So make them all depend on IBM_EMAC being enabled first.Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Thu, 01 Dec 2016 09:50:46 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&gt;</dc:creator>
    </item>
<item>
        <title>577ec789 - powerpc/cell: Drop select of MEMORY_HOTPLUG</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#577ec789</link>
        <description>powerpc/cell: Drop select of MEMORY_HOTPLUGSPU_FS selects MEMORY_HOTPLUG, which is problematic becauseMEMORY_HOTPLUG is user selectable, meaning we can end up with a broken.config where MEMORY_HOTPLUG is enabled but its dependencies are not,leading to build breakages.The select of MEMORY_HOTPLUG for SPU_FS was added back in 2006, incommit 4da30d15b6d5 (&quot;[POWERPC] spufs: fix memory hotplug dependency&quot;).However we reworked the spufs code and removed the dependency on memoryhotplug in 2007 in commit 78bde53e351b (&quot;[POWERPC] spufs: remove needfor struct page for SPEs&quot;).So drop the select as it&apos;s no longer needed and causes problems.Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Thu, 01 Dec 2016 09:50:45 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&gt;</dc:creator>
    </item>
<item>
        <title>24ad1648 - powerpc/cell: Remove the Cell QPACE code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#24ad1648</link>
        <description>powerpc/cell: Remove the Cell QPACE codeAll users of QPACE have upgraded to QPACE2 so remove the Cell QPACE code.Signed-off-by: Rashmica Gupta &lt;rashmicy@gmail.com&gt;Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Tue, 01 Dec 2015 03:51:38 +0000</pubDate>
        <dc:creator>Rashmica Gupta &lt;rashmicy@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>e5e16d8f - powerpc: Kconfig: remove BE-only platforms from LE kernel build</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#e5e16d8f</link>
        <description>powerpc: Kconfig: remove BE-only platforms from LE kernel buildCurrently, little endian is only supported on powernv and pseries,however, Kconfigs still allow us to include other platforms in a LEkernel, this may result in space wasting or even build error if someBE-only platforms always assume they are built for a BE kernel. So justmodify the Kconfigs of BE-only platforms to remove them from being builtfor a LE kernel.For 32bit only platforms, nothing needs to be done, becauseCPU_LITTLE_ENDIAN depends on PPC64. For 64bit supported platforms, addCPU_BIG_ENDIAN to dependencies explicitly, so that these platforms willbe disabled for LE [Suggested-by: C&#233;dric Le Goater &lt;clg@fr.ibm.com&gt;].Signed-off-by: Boqun Feng &lt;boqun.feng@gmail.com&gt;Acked-by: Geoff Levand &lt;geoff@infradead.org&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Sun, 06 Sep 2015 23:58:00 +0000</pubDate>
        <dc:creator>Boqun Feng &lt;boqun.feng@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f444f1f8 - powerpc/cell: Drop support for 64K local store on 4K kernels</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#f444f1f8</link>
        <description>powerpc/cell: Drop support for 64K local store on 4K kernelsBack in the olden days we added support for using 64K pages to map theSPU (Synergistic Processing Unit) local store on Cell, when the mainkernel was using 4K pages.This was useful at the time because distros were using 4K pages, butusing 64K pages on the SPUs could reduce TLB pressure there.However these days the number of Cell users is approaching zero, andsupporting this option adds unpleasant complexity to the memorymanagement code.So drop the option, CONFIG_SPU_FS_64K_LS, and all related code.Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Acked-by: Jeremy Kerr &lt;jk@ozlabs.org&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Fri, 07 Aug 2015 06:19:44 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&gt;</dc:creator>
    </item>
<item>
        <title>bf4981a0 - powerpc: Remove the celleb support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#bf4981a0</link>
        <description>powerpc: Remove the celleb supportThe celleb code has seen no actual development for ~7 years.We (maintainers) have no access to test hardware, and it is highlylikely the code has bit-rotted.As far as we&apos;re aware the hardware was never widely available, and iscertainly no longer available, and no one on the list has shown anyinterest in it over the years.So remove it. If anyone has one and cares please speak up.Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Acked-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;Acked-by: Jeremy Kerr &lt;jk@ozlabs.org&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Thu, 19 Mar 2015 04:15:20 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&gt;</dc:creator>
    </item>
<item>
        <title>e83d0169 - powerpc/cell: Move spu_handle_mm_fault() out of cell platform</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#e83d0169</link>
        <description>powerpc/cell: Move spu_handle_mm_fault() out of cell platformCurrently spu_handle_mm_fault() is in the cell platform.This code is generically useful for other non-cell co-processors on powerpc.This patch moves this function out of the cell platform into arch/powerpc/mm sothat others may use it.Signed-off-by: Ian Munsie &lt;imunsie@au1.ibm.com&gt;Signed-off-by: Michael Neuling &lt;mikey@neuling.org&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Wed, 08 Oct 2014 08:54:50 +0000</pubDate>
        <dc:creator>Ian Munsie &lt;imunsie@au1.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>6eb1c377 - cpufreq: powerpc/platforms/cell: move cpufreq driver to drivers/cpufreq</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#6eb1c377</link>
        <description>cpufreq: powerpc/platforms/cell: move cpufreq driver to drivers/cpufreqThis patch moves cpufreq driver of powerpc platforms/cell to drivers/cpufreq.Signed-off-by: Viresh Kumar &lt;viresh.kumar@linaro.org&gt;Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Mon, 25 Mar 2013 05:50:23 +0000</pubDate>
        <dc:creator>Viresh Kumar &lt;viresh.kumar@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>e274d0bc - arch/powerpc/platforms/cell: remove depends on CONFIG_EXPERIMENTAL</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/platforms/cell/Kconfig#e274d0bc</link>
        <description>arch/powerpc/platforms/cell: remove depends on CONFIG_EXPERIMENTALThe CONFIG_EXPERIMENTAL config item has not carried much meaning for awhile now and is almost always enabled by default. As agreed during theLinux kernel summit, remove it from any &quot;depends on&quot; lines in Kconfigs.CC: Arnd Bergmann &lt;arnd@arndb.de&gt;CC: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;CC: Paul Mackerras &lt;paulus@samba.org&gt;Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/arch/powerpc/platforms/cell/Kconfig</description>
        <pubDate>Thu, 17 Jan 2013 02:53:24 +0000</pubDate>
        <dc:creator>Kees Cook &lt;keescook@chromium.org&gt;</dc:creator>
    </item>
</channel>
</rss>
