<?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>3599bae4 - parisc: Temporarily disable jump label support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#3599bae4</link>
        <description>parisc: Temporarily disable jump label supportThe 32-bit Debian kernel 6.12 fails to boot and crashes like this: init (pid 65): Protection id trap (code 7) CPU: 0 UID: 0 PID: 65 Comm: init Not tainted 6.12.9 #2 Hardware name: 9000/778/B160L      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI PSW: 00000000000001000000000000001111 Not tainted r00-03  0004000f 110d39d0 109a6558 12974400 r04-07  12a810e0 12a810e0 00000000 12a81144 r08-11  12a81174 00000007 00000000 00000002 r12-15  f8c55c08 0000006c 00000001 f8c55c08 r16-19  00000002 f8c58620 002da3a8 0000004e r20-23  00001a46 0000000f 10754f84 00000000 r24-27  00000000 00000003 12ae6980 1127b9d0 r28-31  00000000 00000000 12974440 109a6558 sr00-03  00000000 00000000 00000000 00000010 sr04-07  00000000 00000000 00000000 00000000 IASQ: 00000000 00000000 IAOQ: 110d39d0 110d39d4  IIR: baadf00d    ISR: 00000000  IOR: 110d39d0  CPU:        0   CR30: 128740c0 CR31: 00000000  ORIG_R28: 000003f3  IAOQ[0]: 0x110d39d0  IAOQ[1]: 0x110d39d4  RP(r2): security_sk_free+0x70/0x1a4 Backtrace:  [&lt;10d8c844&gt;] __sk_destruct+0x2bc/0x378  [&lt;10d8e33c&gt;] sk_destruct+0x68/0x8c  [&lt;10d8e3dc&gt;] __sk_free+0x7c/0x148  [&lt;10d8e560&gt;] sk_free+0xb8/0xf0  [&lt;10f6420c&gt;] unix_release_sock+0x3ac/0x50c  [&lt;10f643b8&gt;] unix_release+0x4c/0x7c  [&lt;10d832f8&gt;] __sock_release+0x5c/0xf8  [&lt;10d833b4&gt;] sock_close+0x20/0x44  [&lt;107ba52c&gt;] __fput+0xf8/0x468  [&lt;107baa08&gt;] __fput_sync+0xb4/0xd4  [&lt;107b471c&gt;] sys_close+0x44/0x94  [&lt;10405334&gt;] syscall_exit+0x0/0x10Bisecting points to this commit which triggers the issue:	commit  417c5643cd67a55f424b203b492082035d0236c3	Author: KP Singh &lt;kpsingh@kernel.org&gt;	Date:   Fri Aug 16 17:43:07 2024 +0200	        lsm: replace indirect LSM hook calls with static callsAfter more analysis it seems that we don&apos;t fully implement the static callsand jump tables yet. Additionally the functions which mark kernel memoryread-only or read-write-executable needs to be further enhanced to be able tofully support static calls.Enabling CONFIG_SECURITY_YAMA=y was one possibility to trigger the issue,although YAMA isn&apos;t the reason for the fault.As a temporary solution disable JUMP_LABEL functionality toavoid the crashes.Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;Cc: Guenter Roeck &lt;linux@roeck-us.net&gt;Reviewed-by: Guenter Roeck &lt;linux@roeck-us.net&gt;Cc: &lt;stable@vger.kernel.org&gt; # v6.12+

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Thu, 16 Jan 2025 20:17:47 +0000</pubDate>
        <dc:creator>Helge Deller &lt;deller@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b5ff52be - parisc: Convert to generic clockevents</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#b5ff52be</link>
        <description>parisc: Convert to generic clockeventsConvert parisc timer code to generic clockevents framework.Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Sat, 31 Aug 2024 12:26:53 +0000</pubDate>
        <dc:creator>Helge Deller &lt;deller@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>de6c85bf - dma-mapping: clearly mark DMA ops as an architecture feature</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#de6c85bf</link>
        <description>dma-mapping: clearly mark DMA ops as an architecture featureDMA ops are a helper for architectures and not for drivers to overridethe DMA implementation.Unfortunately driver authors keep ignoring this.  Make the fact moreclear by renaming the symbol to ARCH_HAS_DMA_OPS and having the two driversoverriding their dma_ops depend on that.  These drivers should probably bemarked broken, but we can give them a bit of a grace period for that.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Acked-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt; # for IPU6Acked-by: Robin Murphy &lt;robin.murphy@arm.com&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Wed, 28 Aug 2024 06:02:47 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>7ae04ba3 - parisc: fix a possible DMA corruption</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#7ae04ba3</link>
        <description>parisc: fix a possible DMA corruptionARCH_DMA_MINALIGN was defined as 16 - this is too small - it may bepossible that two unrelated 16-byte allocations share a cache line. Ifone of these allocations is written using DMA and the other is writtenusing cached write, the value that was written with DMA may becorrupted.This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 -that&apos;s the largest possible cache line size.As different parisc microarchitectures have different cache line size, wedefine arch_slab_minalign(), cache_line_size() anddma_get_cache_alignment() so that the kernel may tune slab cacheparameters dynamically, based on the detected cache line size.Signed-off-by: Mikulas Patocka &lt;mpatocka@redhat.com&gt;Cc: stable@vger.kernel.orgSigned-off-by: Helge Deller &lt;deller@gmx.de&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Sat, 27 Jul 2024 18:22:52 +0000</pubDate>
        <dc:creator>Mikulas Patocka &lt;mpatocka@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>cbade823 - parisc: Add support for CONFIG_SYSCTL_ARCH_UNALIGN_NO_WARN</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#cbade823</link>
        <description>parisc: Add support for CONFIG_SYSCTL_ARCH_UNALIGN_NO_WARNAllow users to disable kernel warnings for unaligned memoryaccesses from kernel via the /proc/sys/kernel/ignore-unaligned-usertrapprocfs entry.That way users can disable those warnings in case they happen toooften.Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Sun, 21 Jul 2024 21:36:36 +0000</pubDate>
        <dc:creator>Helge Deller &lt;deller@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>4c29ab84 - parisc: Fix warning at drivers/pci/msi/msi.h:121</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#4c29ab84</link>
        <description>parisc: Fix warning at drivers/pci/msi/msi.h:121Fix warning at drivers/pci/msi/msi.h:121.Recently, I added a PCI to PCIe bridge adaptor and a PCIe NVME cardto my rp3440. Then, I noticed this warning at boot: WARNING: CPU: 0 PID: 10 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x68/0x90 CPU: 0 PID: 10 Comm: kworker/u32:0 Not tainted 6.9.7-parisc64 #1  Debian 6.9.7-1 Hardware name: 9000/800/rp3440 Workqueue: async async_run_entry_fnWe need to select PCI_MSI_ARCH_FALLBACKS when PCI_MSI is selected.Signed-off-by: John David Anglin &lt;dave.anglin@bell.net&gt;Cc: stable@vger.kernel.org	# v6.0+Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Mon, 01 Jul 2024 13:42:41 +0000</pubDate>
        <dc:creator>John David Anglin &lt;dave@mx3210.local&gt;</dc:creator>
    </item>
<item>
        <title>403f17a3 - parisc: use generic sys_fanotify_mark implementation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#403f17a3</link>
        <description>parisc: use generic sys_fanotify_mark implementationThe sys_fanotify_mark() syscall on parisc uses the reverse word orderfor the two halves of the 64-bit argument compared to all syscalls onall 32-bit architectures. As far as I can tell, the problem is thatthe function arguments on parisc are sorted backwards (26, 25, 24, 23,...) compared to everyone else, so the calling conventions of using aneven/odd register pair in native word order result in the lower wordcoming first in function arguments, matching the expected behavioron little-endian architectures. The system call conventions howeverended up matching what the other 32-bit architectures do.A glibc cleanup in 2020 changed the userspace behavior in a way thathandles all architectures consistently, but this inadvertently brokeparisc32 by changing to the same method as everyone else.The change made it into glibc-2.35 and subsequently into debian 12(bookworm), which is the latest stable release. This means weneed to choose between reverting the glibc change or changing thekernel to match it again, but either hange will leave some systemsbroken.Pick the option that is more likely to help current and futureusers and change the kernel to match current glibc. This alsomeans the behavior is now consistent across architectures, butit breaks running new kernels with old glibc builds before 2.35.Link: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d150181d73d9Link: https://git.kernel.org/pub/scm/linux/kernel/git/history/history.git/commit/arch/parisc/kernel/sys_parisc.c?h=57b1dfbd5b4a39dCc: Adhemerval Zanella &lt;adhemerval.zanella@linaro.org&gt;Tested-by: Helge Deller &lt;deller@gmx.de&gt;Acked-by: Helge Deller &lt;deller@gmx.de&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;---I found this through code inspection, please double-check to makesure I got the bug and the fix right.The alternative is to fix this by reverting glibc back to theunusual behavior.

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Fri, 07 Jun 2024 11:40:45 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>d3e5bab9 - arch: simplify architecture specific page size configuration</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#d3e5bab9</link>
        <description>arch: simplify architecture specific page size configurationarc, arm64, parisc and powerpc all have their own Kconfig symbolsin place of the common CONFIG_PAGE_SIZE_4KB symbols. Change theseso the common symbols are the ones that are actually used, whileleaving the arhcitecture specific ones as the user visibleplace for configuring it, to avoid breaking user configs.Reviewed-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt; (powerpc32)Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Acked-by: Helge Deller &lt;deller@gmx.de&gt; # pariscReviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Mon, 26 Feb 2024 16:14:12 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>8690bbcf - Introduce cpu_dcache_is_aliasing() across all architectures</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#8690bbcf</link>
        <description>Introduce cpu_dcache_is_aliasing() across all architecturesIntroduce a generic way to query whether the data cache is virtuallyaliased on all architectures. Its purpose is to ensure that subsystemswhich are incompatible with virtually aliased data caches (e.g. FS_DAX)can reliably query this.For data cache aliasing, there are three scenarios dependending on thearchitecture. Here is a breakdown based on my understanding:A) The data cache is always aliasing:* arc* csky* m68k (note: shared memory mappings are incoherent ? SHMLBA is missing there.)* sh* pariscB) The data cache aliasing is statically known or depends on querying CPU   state at runtime:* arm (cache_is_vivt() || cache_is_vipt_aliasing())* mips (cpu_has_dc_aliases)* nios2 (NIOS2_DCACHE_SIZE &gt; PAGE_SIZE)* sparc32 (vac_cache_size &gt; PAGE_SIZE)* sparc64 (L1DCACHE_SIZE &gt; PAGE_SIZE)* xtensa (DCACHE_WAY_SIZE &gt; PAGE_SIZE)C) The data cache is never aliasing:* alpha* arm64 (aarch64)* hexagon* loongarch (but with incoherent write buffers, which are disabled since             commit d23b7795 (&quot;LoongArch: Change SHMLBA from SZ_64K to PAGE_SIZE&quot;))* microblaze* openrisc* powerpc* riscv* s390* um* x86Require architectures in A) and B) to select ARCH_HAS_CPU_CACHE_ALIASING andimplement &quot;cpu_dcache_is_aliasing()&quot;.Architectures in C) don&apos;t select ARCH_HAS_CPU_CACHE_ALIASING, and thuscpu_dcache_is_aliasing() simply evaluates to &quot;false&quot;.Note that this leaves &quot;cpu_icache_is_aliasing()&quot; to be implemented as futurework. This would be useful to gate features like XIP on architectureswhich have aliasing CPU dcache-icache but not CPU dcache-dcache.Use &quot;cpu_dcache&quot; and &quot;cpu_cache&quot; rather than just &quot;dcache&quot; and &quot;cache&quot;to clarify that we really mean &quot;CPU data cache&quot; and &quot;CPU cache&quot; toeliminate any possible confusion with VFS &quot;dentry cache&quot; and &quot;pagecache&quot;.Link: https://lore.kernel.org/lkml/20030910210416.GA24258@mail.jlokier.co.uk/Link: https://lkml.kernel.org/r/20240215144633.96437-9-mathieu.desnoyers@efficios.comFixes: d92576f1167c (&quot;dax: does not work correctly with virtual aliasing caches&quot;)Signed-off-by: Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;Cc: Dan Williams &lt;dan.j.williams@intel.com&gt;Cc: Vishal Verma &lt;vishal.l.verma@intel.com&gt;Cc: Dave Jiang &lt;dave.jiang@intel.com&gt;Cc: Matthew Wilcox &lt;willy@infradead.org&gt;Cc: Arnd Bergmann &lt;arnd@arndb.de&gt;Cc: Russell King &lt;linux@armlinux.org.uk&gt;Cc: Alasdair Kergon &lt;agk@redhat.com&gt;Cc: Christoph Hellwig &lt;hch@lst.de&gt;Cc: Dave Chinner &lt;david@fromorbit.com&gt;Cc: Heiko Carstens &lt;hca@linux.ibm.com&gt;Cc: kernel test robot &lt;lkp@intel.com&gt;Cc: Michael Sclafani &lt;dm-devel@lists.linux.dev&gt;Cc: Mike Snitzer &lt;snitzer@kernel.org&gt;Cc: Mikulas Patocka &lt;mpatocka@redhat.com&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Thu, 15 Feb 2024 14:46:32 +0000</pubDate>
        <dc:creator>Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;</dc:creator>
    </item>
<item>
        <title>cd14b018 - treewide: replace or remove redundant def_bool in Kconfig files</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#cd14b018</link>
        <description>treewide: replace or remove redundant def_bool in Kconfig files&apos;def_bool X&apos; is a shorthand for &apos;bool&apos; plus &apos;default X&apos;.&apos;def_bool&apos; is redundant where &apos;bool&apos; is already present, so &apos;def_bool X&apos;can be replaced with &apos;default X&apos;, or removed if X is &apos;n&apos;.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Sun, 11 Feb 2024 12:48:08 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>918327e9 - ubsan: Remove CONFIG_UBSAN_SANITIZE_ALL</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#918327e9</link>
        <description>ubsan: Remove CONFIG_UBSAN_SANITIZE_ALLFor simplicity in splitting out UBSan options into separate rules,remove CONFIG_UBSAN_SANITIZE_ALL, effectively defaulting to &quot;y&quot;, whichis how it is generally used anyway. (There are no &quot;:= y&quot; cases beyondwhere a specific file is enabled when a top-level &quot;:= n&quot; is in effect.)Cc: Andrey Konovalov &lt;andreyknvl@gmail.com&gt;Cc: Marco Elver &lt;elver@google.com&gt;Cc: linux-doc@vger.kernel.orgCc: linux-kbuild@vger.kernel.orgSigned-off-by: Kees Cook &lt;keescook@chromium.org&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Sun, 28 Jan 2024 18:45:29 +0000</pubDate>
        <dc:creator>Kees Cook &lt;keescook@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>8b1d7239 - parisc: Fix random data corruption from exception handler</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#8b1d7239</link>
        <description>parisc: Fix random data corruption from exception handlerThe current exception handler implementation, which assists when accessinguser space memory, may exhibit random data corruption if the compiler decidesto use a different register than the specified register %r29 (defined inASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose anotherregister, the fault handler will nevertheless store -EFAULT into %r29 and thustrash whatever this register is used for.Looking at the assembly I found that this happens sometimes in emulate_ldd().To solve the issue, the easiest solution would be if it somehow ispossible to tell the fault handler which register is used to hold the errorcode. Using %0 or %1 in the inline assembly is not posssible as it will showup as e.g. %r29 (with the &quot;%r&quot; prefix), which the GNU assembler can notconvert to an integer.This patch takes another, better and more flexible approach:We extend the __ex_table (which is out of the execution path) by one 32-word.In this word we tell the compiler to insert the assembler instruction&quot;or %r0,%r0,%reg&quot;, where %reg references the register which the compilerchoosed for the error return code.In case of an access failure, the fault handler finds the __ex_table entry andcan examine the opcode. The used register is encoded in the lowest 5 bits, andthe fault handler can then store -EFAULT into this register.Since we extend the __ex_table to 3 words we can&apos;t use the BUILDTIME_TABLE_SORTconfig option any longer.Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;Cc: &lt;stable@vger.kernel.org&gt; # v6.0+

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Sat, 20 Jan 2024 14:29:27 +0000</pubDate>
        <dc:creator>Helge Deller &lt;deller@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>43266838 - parisc: Reduce size of the bug_table on 64-bit kernel by half</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#43266838</link>
        <description>parisc: Reduce size of the bug_table on 64-bit kernel by halfEnable GENERIC_BUG_RELATIVE_POINTERS which will store 32-bit relativeoffsets to the bug address and the source file name instead of 64-bitabsolute addresses. This effectively reduces the size of thebug_table[] array by half on 64-bit kernels.Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Thu, 23 Nov 2023 20:57:19 +0000</pubDate>
        <dc:creator>Helge Deller &lt;deller@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>5f74f820 - parisc: fix mmap_base calculation when stack grows upwards</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#5f74f820</link>
        <description>parisc: fix mmap_base calculation when stack grows upwardsMatoro reported various userspace crashes on the parisc platform with kernel6.6 and bisected it to commit 3033cd430768 (&quot;parisc: Use generic mmap top-downlayout and brk randomization&quot;).That commit switched parisc to use the common infrastructure to calculatemmap_base, but missed that the mmap_base() function takes care forarchitectures where the stack grows downwards only.Fix the mmap_base() calculation to include the stack-grows-upwards caseand thus fix the userspace crashes on parisc.Link: https://lkml.kernel.org/r/ZVH2qeS1bG7/1J/l@p100Fixes: 3033cd430768 (&quot;parisc: Use generic mmap top-down layout and brk randomization&quot;)Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;Reported-by: matoro &lt;matoro_mailinglist_kernel@matoro.tk&gt;Tested-by: matoro &lt;matoro_mailinglist_kernel@matoro.tk&gt;Cc: &lt;stable@vger.kernel.org&gt;	[6.6+]Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Mon, 13 Nov 2023 10:12:57 +0000</pubDate>
        <dc:creator>Helge Deller &lt;deller@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>01fef826 - parisc: Allow building uncompressed Linux kernel</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#01fef826</link>
        <description>parisc: Allow building uncompressed Linux kernelAdd HAVE_KERNEL_UNCOMPRESSED flag and fix build in bootdirectory.Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Tue, 17 Oct 2023 19:00:11 +0000</pubDate>
        <dc:creator>Helge Deller &lt;deller@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>2c8ed1b9 - dma-direct: add a CONFIG_ARCH_HAS_DMA_ALLOC symbol</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#2c8ed1b9</link>
        <description>dma-direct: add a CONFIG_ARCH_HAS_DMA_ALLOC symbolInstead of using arch_dma_alloc if none of the generic coherentallocators are used, require the architectures to explicitly opt intoproviding it.  This will used to deal with the case of m68knommu andcoldfire where we can&apos;t do any coherent allocations whatsoever, andalso makes it clear that arch_dma_alloc is a last resort.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Robin Murphy &lt;robin.murphy@arm.com&gt;Reviewed-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Tested-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Thu, 05 Oct 2023 07:05:36 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>4800a621 - parisc: Wire up eBPF JIT compiler</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#4800a621</link>
        <description>parisc: Wire up eBPF JIT compilerSigned-off-by: Helge Deller &lt;deller@gmx.de&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Thu, 17 Aug 2023 21:45:02 +0000</pubDate>
        <dc:creator>Helge Deller &lt;deller@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>3033cd43 - parisc: Use generic mmap top-down layout and brk randomization</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#3033cd43</link>
        <description>parisc: Use generic mmap top-down layout and brk randomizationparisc uses a top-down layout by default that exactly fits the genericfunctions, so get rid of arch specific code and use the generic versionby selecting ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT.Note that on parisc the stack always grows up and a &quot;unlimited stack&quot;simply means that the value as defined in CONFIG_STACK_MAX_DEFAULT_SIZE_MBshould be used. So RLIM_INFINITY is not an indicator to use the legacymemory layout.Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Fri, 18 Aug 2023 22:53:28 +0000</pubDate>
        <dc:creator>Helge Deller &lt;deller@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>b9bf5cb1 - parisc/kexec: refactor for kernel/Kconfig.kexec</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#b9bf5cb1</link>
        <description>parisc/kexec: refactor for kernel/Kconfig.kexecThe kexec and crash kernel options are provided in the commonkernel/Kconfig.kexec. Utilize the common options and providethe ARCH_SUPPORTS_ and ARCH_SELECTS_ entries to recreate theequivalent set of KEXEC and CRASH options.Link: https://lkml.kernel.org/r/20230712161545.87870-10-eric.devolder@oracle.comSigned-off-by: Eric DeVolder &lt;eric.devolder@oracle.com&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Wed, 12 Jul 2023 16:15:40 +0000</pubDate>
        <dc:creator>Eric DeVolder &lt;eric.devolder@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>426b313f - parisc: mm: convert to GENERIC_IOREMAP</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/parisc/Kconfig#426b313f</link>
        <description>parisc: mm: convert to GENERIC_IOREMAPBy taking GENERIC_IOREMAP method, the generic generic_ioremap_prot(),generic_iounmap(), and their generic wrapper ioremap_prot(), ioremap() andiounmap() are all visible and available to arch.  Arch needs to providewrapper functions to override the generic versions if there&apos;s archspecific handling in its ioremap_prot(), ioremap() or iounmap().  Thischange will simplify implementation by removing duplicated code withgeneric_ioremap_prot() and generic_iounmap(), and has the equivalentfunctioality as before.Here, add wrapper function ioremap_prot() for parisc&apos;s special operationwhen iounmap().Link: https://lkml.kernel.org/r/20230706154520.11257-15-bhe@redhat.comSigned-off-by: Baoquan He &lt;bhe@redhat.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Mike Rapoport (IBM) &lt;rppt@kernel.org&gt;Acked-by: Helge Deller &lt;deller@gmx.de&gt;Cc: &quot;James E.J. Bottomley&quot; &lt;James.Bottomley@HansenPartnership.com&gt;Cc: Helge Deller &lt;deller@gmx.de&gt;Cc: Alexander Gordeev &lt;agordeev@linux.ibm.com&gt;Cc: Arnd Bergmann &lt;arnd@arndb.de&gt;Cc: Brian Cain &lt;bcain@quicinc.com&gt;Cc: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Cc: Christian Borntraeger &lt;borntraeger@linux.ibm.com&gt;Cc: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Cc: Chris Zankel &lt;chris@zankel.net&gt;Cc: David Laight &lt;David.Laight@ACULAB.COM&gt;Cc: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Cc: Gerald Schaefer &lt;gerald.schaefer@linux.ibm.com&gt;Cc: Heiko Carstens &lt;hca@linux.ibm.com&gt;Cc: John Paul Adrian Glaubitz &lt;glaubitz@physik.fu-berlin.de&gt;Cc: Jonas Bonn &lt;jonas@southpole.se&gt;Cc: Kefeng Wang &lt;wangkefeng.wang@huawei.com&gt;Cc: Matthew Wilcox &lt;willy@infradead.org&gt;Cc: Max Filippov &lt;jcmvbkbc@gmail.com&gt;Cc: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Cc: Nathan Chancellor &lt;nathan@kernel.org&gt;Cc: Nicholas Piggin &lt;npiggin@gmail.com&gt;Cc: Niklas Schnelle &lt;schnelle@linux.ibm.com&gt;Cc: Rich Felker &lt;dalias@libc.org&gt;Cc: Stafford Horne &lt;shorne@gmail.com&gt;Cc: Stefan Kristiansson &lt;stefan.kristiansson@saunalahti.fi&gt;Cc: Sven Schnelle &lt;svens@linux.ibm.com&gt;Cc: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Cc: Vineet Gupta &lt;vgupta@kernel.org&gt;Cc: Will Deacon &lt;will@kernel.org&gt;Cc: Yoshinori Sato &lt;ysato@users.sourceforge.jp&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/arch/parisc/Kconfig</description>
        <pubDate>Thu, 06 Jul 2023 15:45:15 +0000</pubDate>
        <dc:creator>Baoquan He &lt;bhe@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
