<?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>dcce8548 - m68k: coldfire: select PCI_IOMAP for PCI</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#dcce8548</link>
        <description>m68k: coldfire: select PCI_IOMAP for PCIAfter I dropped CONFIG_GENERIC_IOMAP, some PCI drivers started failingto link when CONFIG_MMU is disabled:ERROR: modpost: &quot;pci_iounmap&quot; [drivers/video/fbdev/i740fb.ko] undefined!ERROR: modpost: &quot;pci_iounmap&quot; [drivers/video/fbdev/vt8623fb.ko] undefined!ERROR: modpost: &quot;pci_iomap_wc&quot; [drivers/video/fbdev/vt8623fb.ko] undefined!ERROR: modpost: &quot;pci_iomap&quot; [drivers/video/fbdev/vt8623fb.ko] undefined!ERROR: modpost: &quot;pci_iounmap&quot; [drivers/video/fbdev/s3fb.ko] undefined!...It turns out that there were two mistakes in my patch: on !MMU I forgotto enable CONFIG_GENERIC_PCI_IOMAP, and for Coldfire with MMU enabled,teh GENERIC_IOMAP was left in place but incorrectly configured.Fixes: 9d48cc07d0d7 (&quot;m68k/nommu: stop using GENERIC_IOMAP&quot;)Reported-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Acked-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Mon, 24 Mar 2025 06:53:47 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>9d48cc07 - m68k/nommu: stop using GENERIC_IOMAP</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#9d48cc07</link>
        <description>m68k/nommu: stop using GENERIC_IOMAPThere is no need to go through the GENERIC_IOMAP wrapper for PIO onnommu platforms, since these always come from PCI I/O space that isitself memory mapped.Instead, the generic ioport_map() can just return the MMIO locationof the ports directly by applying the PCI_IO_PA offset, whileioread32/iowrite32 trivially turn into readl/writel as they doon most other architectures.Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Tue, 11 Mar 2025 11:01:13 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>e419ddea - m68k: Use kernel&apos;s generic muldi3 libgcc function</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#e419ddea</link>
        <description>m68k: Use kernel&apos;s generic muldi3 libgcc functionUse the kernels own generic lib/muldi3.c implementation of muldi3 for68K machines. Some 68K CPUs support 64bit multiplies so move the archspecific umul_ppmm() macro into a header file that is included bylib/muldi3.c. That way it can take advantage of the single instructionwhen available.There does not appear to be any existing mechanism for the genericlib/muldi3.c code to pick up an external arch definition of umul_ppmm().Create an arch specific libgcc.h that can optionally be included bythe system include/linux/libgcc.h to allow for this.Somewhat oddly there is also a similar definition of umul_ppmm() inthe non-architecture code in lib/crypto/mpi/longlong.h for a wide rangeor machines. Its presence ends up complicating the include setup andmeans not being able to use something like compiler.h instead. Actuallythere is a few other defines of umul_ppmm() macros spread around invarious architectures, but not directly usable for the m68k case.Signed-off-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Link: https://lore.kernel.org/20231113133209.1367286-1-gerg@linux-m68k.orgReviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Reviewed-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Mon, 13 Nov 2023 13:32:09 +0000</pubDate>
        <dc:creator>Greg Ungerer &lt;gerg@linux-m68k.org&gt;</dc:creator>
    </item>
<item>
        <title>5d42a685 - m68k: Move Sun 3 into a top-level platform option</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#5d42a685</link>
        <description>m68k: Move Sun 3 into a top-level platform optionIt is possible to select an m68k MMU build but not actually enable anyof the three MMU options, which then results in a build failure:    arch/m68k/include/asm/page.h:10:25: error: &apos;CONFIG_PAGE_SHIFT&apos; undeclared here (not in a function); did you mean &apos;CONFIG_LOG_BUF_SHIFT&apos;?Change the Kconfig selection to ensure that exactly one of the threeoptions is always enabled whenever an MMU-enabled kernel is built, butmoving CONFIG_SUN3 into a top-level option next to M68KCLASSIC andCOLDFIRE.All defconfig files should keep working without changes, butalldefconfig now builds support for the classic MMU.Reported-by: kernel test robot &lt;lkp@intel.com&gt;Closes: https://lore.kernel.org/oe-kbuild-all/202408032138.P7sBvIns-lkp@intel.com/Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Link: https://lore.kernel.org/20241030195638.22542-1-arnd@kernel.orgSigned-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Wed, 30 Oct 2024 19:56:13 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>c66b7b95 - m68k: Move ARCH_HAS_CPU_CACHE_ALIASING</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#c66b7b95</link>
        <description>m68k: Move ARCH_HAS_CPU_CACHE_ALIASINGMove the recently added ARCH_HAS_CPU_CACHE_ALIASING to restorealphabetical sort order.Fixes: 8690bbcf3b7010b3 (&quot;Introduce cpu_dcache_is_aliasing() across all architectures&quot;)Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Reviewed-by: Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;Link: https://lore.kernel.org/r/4574ad6cc1117e4b5d29812c165bf7f6e5b60773.1714978406.git.geert@linux-m68k.org

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Mon, 06 May 2024 07:06:41 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;</dc:creator>
    </item>
<item>
        <title>40d43887 - m68k: Let GENERIC_IOMAP depend on HAS_IOPORT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#40d43887</link>
        <description>m68k: Let GENERIC_IOMAP depend on HAS_IOPORTIn a future patch HAS_IOPORT=n will disable inb()/outb() and friends atcompile time. With that choosing dynamically between I/O port and MMIOaccess via GNERIC_IOMAP will not work. So only select GENERIC_IOMAP whenHAS_IOPORT is selected.Co-developed-by: Arnd Bergmann &lt;arnd@kernel.org&gt;Signed-off-by: Arnd Bergmann &lt;arnd@kernel.org&gt;Signed-off-by: Niklas Schnelle &lt;schnelle@linux.ibm.com&gt;Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Link: https://lore.kernel.org/r/20240403122851.38808-2-schnelle@linux.ibm.comSigned-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Wed, 03 Apr 2024 12:28:51 +0000</pubDate>
        <dc:creator>Niklas Schnelle &lt;schnelle@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>5394f1e9 - arch: define CONFIG_PAGE_SIZE_*KB on all architectures</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#5394f1e9</link>
        <description>arch: define CONFIG_PAGE_SIZE_*KB on all architecturesMost architectures only support a single hardcoded page size. In orderto ensure that each one of these sets the corresponding Kconfig symbols,change over the PAGE_SHIFT definition to the common one and allowonly the hardware page size to be selected.Acked-by: Guo Ren &lt;guoren@kernel.org&gt;Acked-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;Acked-by: Stafford Horne &lt;shorne@gmail.com&gt;Acked-by: Johannes Berg &lt;johannes@sipsolutions.net&gt;Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Reviewed-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/m68k/Kconfig</description>
        <pubDate>Mon, 26 Feb 2024 16:14:13 +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/m68k/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/m68k/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>7a360df9 - m68k: don&apos;t provide arch_dma_alloc for nommu/coldfire</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#7a360df9</link>
        <description>m68k: don&apos;t provide arch_dma_alloc for nommu/coldfireColdfire cores configured with a data cache can&apos;t provide coherentDMA allocations at all.Instead of returning non-coherent kernel memory in this case,return NULL and fail the allocation.The only driver that used to rely on the previous behavior (fec) hasbeen switched to use non-coherent allocations for this case recently.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&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/m68k/Kconfig</description>
        <pubDate>Thu, 12 Oct 2023 07:52:27 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>9e28bf8b - m68k: use the coherent DMA code for coldfire without data cache</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#9e28bf8b</link>
        <description>m68k: use the coherent DMA code for coldfire without data cacheColdfire cores configured without a data cache are DMA coherent andshould thus simply use the simple coherent version of dma-direct.Introduce a new COLDFIRE_COHERENT_DMA Kconfig symbol as a convenientshort hand for such configurations, and a M68K_NONCOHERENT_DMA symbolfor all cases where we need to build non-coherent DMA infrastructureto simplify the Kconfig and code conditionals.Not building the non-coherent DMA code slightly reduces the codesize for such configurations.Numers for m5249evb_defconfig below:  text	   data	    bss	    dec	    hex	filename2896158	 401052	  65392	3362602	 334f2a	vmlinux.before2895166	 400988	  65392	3361546	 334b0a	vmlinux.afterSigned-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Tested-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Tue, 17 Oct 2023 14:04:42 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.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/m68k/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/m68k/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>a0938a8e - m68k: Use kernel&apos;s generic libgcc functions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#a0938a8e</link>
        <description>m68k: Use kernel&apos;s generic libgcc functionsThe arch/m68k/lib versions of the libgcc functions: ashldi3, ashrdi3and lshrdi3 were taken directly from an older version of gcc.We can use the kernel&apos;s own generic lib versions of these - they arevirtually identical. Switch to those and remove the m68k local ones.Signed-off-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Link: https://lore.kernel.org/r/20230913071350.1939818-1-gerg@kernel.orgSigned-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Wed, 13 Sep 2023 07:13:50 +0000</pubDate>
        <dc:creator>Greg Ungerer &lt;gerg@linux-m68k.org&gt;</dc:creator>
    </item>
<item>
        <title>a7cc67de - m68k/kexec: refactor for kernel/Kconfig.kexec</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#a7cc67de</link>
        <description>m68k/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-8-eric.devolder@oracle.comSigned-off-by: Eric DeVolder &lt;eric.devolder@oracle.com&gt;Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Wed, 12 Jul 2023 16:15:38 +0000</pubDate>
        <dc:creator>Eric DeVolder &lt;eric.devolder@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>9ceecc25 - m68k/cpu: Switch to arch_cpu_finalize_init()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#9ceecc25</link>
        <description>m68k/cpu: Switch to arch_cpu_finalize_init()check_bugs() is about to be phased out. Switch over to the newarch_cpu_finalize_init() implementation.No functional change.Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Link: https://lore.kernel.org/r/20230613224545.254342916@linutronix.de

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Tue, 13 Jun 2023 23:39:30 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>fcbfe812 - Kconfig: introduce HAS_IOPORT option and select it as necessary</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#fcbfe812</link>
        <description>Kconfig: introduce HAS_IOPORT option and select it as necessaryWe introduce a new HAS_IOPORT Kconfig option to indicate support for I/OPort access. In a future patch HAS_IOPORT=n will disable compilation ofthe I/O accessor functions inb()/outb() and friends on architectureswhich can not meaningfully support legacy I/O spaces such as s390.The following architectures do not select HAS_IOPORT:* ARC* C-SKY* Hexagon* Nios II* OpenRISC* s390* User-Mode Linux* XtensaAll other architectures select HAS_IOPORT at least conditionally.The &quot;depends on&quot; relations on HAS_IOPORT in drivers as well as ifdefsfor HAS_IOPORT specific sections will be added in subsequent patches ona per subsystem basis.Co-developed-by: Arnd Bergmann &lt;arnd@kernel.org&gt;Signed-off-by: Arnd Bergmann &lt;arnd@kernel.org&gt;Acked-by: Johannes Berg &lt;johannes@sipsolutions.net&gt; # for ARCH=umAcked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Signed-off-by: Niklas Schnelle &lt;schnelle@linux.ibm.com&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Thu, 23 Mar 2023 16:33:52 +0000</pubDate>
        <dc:creator>Niklas Schnelle &lt;schnelle@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>6baaade1 - m68k: Add kernel seccomp support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#6baaade1</link>
        <description>m68k: Add kernel seccomp supportAdd secure_computing() call to syscall_trace_enter to actuallyfilter system calls.Add necessary arch Kconfig options, define TIF_SECCOMP traceflag and provide basic seccomp filter support in asm/syscall.hsyscall_get_nr currently uses the syscall nr stored in orig_d0because we change d0 to a default return code before starting asyscall trace. This may be inconsistent with syscall_rollbackcopying orig_d0 to d0 (which we never check upon return fromtrace). We use d0 for the return code from syscall_trace_enterin entry.S currently, and could perhaps expand that to storea new syscall number returned by the seccomp filter beforeexecuting the syscall. This clearly needs some discussion.seccomp_bpf self test on ARAnyM passes 81 out of 94 tests.Signed-off-by: Michael Schmitz &lt;schmitzmic@gmail.com&gt;Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Link: https://lore.kernel.org/r/20230112035529.13521-3-schmitzmic@gmail.comSigned-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Thu, 12 Jan 2023 03:55:28 +0000</pubDate>
        <dc:creator>Michael Schmitz &lt;schmitzmic@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d355a08e - m68k: Allow kexec on M68KCLASSIC with MMU enabled only</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#d355a08e</link>
        <description>m68k: Allow kexec on M68KCLASSIC with MMU enabled onlyNone of the no-MMU CPU types (classic or ColdFire) or ColdFire withMMU enabled have support for kexec yet, so the configuration as itstands is not quite right, and it will fail to compile on them.Make CONFIG_KEXEC depend on both CONFIG_M68KCLASSIC and CONFIG_MMU.Signed-off-by: Greg Ungerer &lt;gerg@linux-m68k.org&gt;Link: https://lore.kernel.org/r/20220831012539.3416470-1-gerg@linux-m68k.orgSigned-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Wed, 31 Aug 2022 01:25:39 +0000</pubDate>
        <dc:creator>Greg Ungerer &lt;gerg@linux-m68k.org&gt;</dc:creator>
    </item>
<item>
        <title>3d923c5f - mm/mmap: drop ARCH_HAS_VM_GET_PAGE_PROT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#3d923c5f</link>
        <description>mm/mmap: drop ARCH_HAS_VM_GET_PAGE_PROTNow all the platforms enable ARCH_HAS_GET_PAGE_PROT.  They define andexport own vm_get_page_prot() whether custom or standardDECLARE_VM_GET_PAGE_PROT.  Hence there is no need for default genericfallback for vm_get_page_prot().  Just drop this fallback and alsoARCH_HAS_GET_PAGE_PROT mechanism.Link: https://lkml.kernel.org/r/20220711070600.2378316-27-anshuman.khandual@arm.comSigned-off-by: Anshuman Khandual &lt;anshuman.khandual@arm.com&gt;Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&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: Christoph Hellwig &lt;hch@infradead.org&gt;Cc: Chris Zankel &lt;chris@zankel.net&gt;Cc: &quot;David S. Miller&quot; &lt;davem@davemloft.net&gt;Cc: Dinh Nguyen &lt;dinguyen@kernel.org&gt;Cc: Guo Ren &lt;guoren@kernel.org&gt;Cc: Heiko Carstens &lt;hca@linux.ibm.com&gt;Cc: Huacai Chen &lt;chenhuacai@kernel.org&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: &quot;James E.J. Bottomley&quot; &lt;James.Bottomley@HansenPartnership.com&gt;Cc: Jeff Dike &lt;jdike@addtoit.com&gt;Cc: Jonas Bonn &lt;jonas@southpole.se&gt;Cc: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Cc: Michal Simek &lt;monstr@monstr.eu&gt;Cc: Nicholas Piggin &lt;npiggin@gmail.com&gt;Cc: Palmer Dabbelt &lt;palmer@dabbelt.com&gt;Cc: Paul Mackerras &lt;paulus@samba.org&gt;Cc: Paul Walmsley &lt;paul.walmsley@sifive.com&gt;Cc: Richard Henderson &lt;rth@twiddle.net&gt;Cc: Rich Felker &lt;dalias@libc.org&gt;Cc: Russell King &lt;linux@armlinux.org.uk&gt;Cc: Sam Ravnborg &lt;sam@ravnborg.org&gt;Cc: Stafford Horne &lt;shorne@gmail.com&gt;Cc: Thomas Bogendoerfer &lt;tsbogend@alpha.franken.de&gt;Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;Cc: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Cc: Vineet Gupta &lt;vgupta@kernel.org&gt;Cc: WANG Xuerui &lt;kernel@xen0n.name&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/m68k/Kconfig</description>
        <pubDate>Mon, 11 Jul 2022 07:06:00 +0000</pubDate>
        <dc:creator>Anshuman Khandual &lt;anshuman.khandual@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>6d0b9225 - m68k/mm: enable ARCH_HAS_VM_GET_PAGE_PROT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#6d0b9225</link>
        <description>m68k/mm: enable ARCH_HAS_VM_GET_PAGE_PROTThis enables ARCH_HAS_VM_GET_PAGE_PROT on the platform and exportsstandard vm_get_page_prot() implementation via DECLARE_VM_GET_PAGE_PROT,which looks up a private and static protection_map[] array.  Subsequentlyall __SXXX and __PXXX macros can be dropped which are no longer needed.Link: https://lkml.kernel.org/r/20220711070600.2378316-22-anshuman.khandual@arm.comSigned-off-by: Anshuman Khandual &lt;anshuman.khandual@arm.com&gt;Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Cc: Thomas Bogendoerfer &lt;tsbogend@alpha.franken.de&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: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Cc: Christoph Hellwig &lt;hch@infradead.org&gt;Cc: Christoph Hellwig &lt;hch@lst.de&gt;Cc: Chris Zankel &lt;chris@zankel.net&gt;Cc: &quot;David S. Miller&quot; &lt;davem@davemloft.net&gt;Cc: Dinh Nguyen &lt;dinguyen@kernel.org&gt;Cc: Guo Ren &lt;guoren@kernel.org&gt;Cc: Heiko Carstens &lt;hca@linux.ibm.com&gt;Cc: Huacai Chen &lt;chenhuacai@kernel.org&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: &quot;James E.J. Bottomley&quot; &lt;James.Bottomley@HansenPartnership.com&gt;Cc: Jeff Dike &lt;jdike@addtoit.com&gt;Cc: Jonas Bonn &lt;jonas@southpole.se&gt;Cc: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Cc: Michal Simek &lt;monstr@monstr.eu&gt;Cc: Nicholas Piggin &lt;npiggin@gmail.com&gt;Cc: Palmer Dabbelt &lt;palmer@dabbelt.com&gt;Cc: Paul Mackerras &lt;paulus@samba.org&gt;Cc: Paul Walmsley &lt;paul.walmsley@sifive.com&gt;Cc: Richard Henderson &lt;rth@twiddle.net&gt;Cc: Rich Felker &lt;dalias@libc.org&gt;Cc: Russell King &lt;linux@armlinux.org.uk&gt;Cc: Sam Ravnborg &lt;sam@ravnborg.org&gt;Cc: Stafford Horne &lt;shorne@gmail.com&gt;Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;Cc: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Cc: Vineet Gupta &lt;vgupta@kernel.org&gt;Cc: WANG Xuerui &lt;kernel@xen0n.name&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/m68k/Kconfig</description>
        <pubDate>Mon, 11 Jul 2022 07:05:55 +0000</pubDate>
        <dc:creator>Anshuman Khandual &lt;anshuman.khandual@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>4313a249 - arch/*/: remove CONFIG_VIRT_TO_BUS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/m68k/Kconfig#4313a249</link>
        <description>arch/*/: remove CONFIG_VIRT_TO_BUSAll architecture-independent users of virt_to_bus() and bus_to_virt()have been fixed to use the dma mapping interfaces or have beenremoved now.  This means the definitions on most architectures, and theCONFIG_VIRT_TO_BUS symbol are now obsolete and can be removed.The only exceptions to this are a few network and scsi drivers for m68kAmiga and VME machines and ppc32 Macintosh. These drivers work correctlywith the old interfaces and are probably not worth changing.On alpha and parisc, virt_to_bus() were still used in asm/floppy.h.alpha can use isa_virt_to_bus() like x86 does, and parisc can justopen-code the virt_to_phys() here, as this is architecture specificcode.I tried updating the bus-virt-phys-mapping.rst documentation, whichstarted as an email from Linus to explain some details of the Linux-2.0driver interfaces. The bits about virt_to_bus() were declared obsoletebackin 2000, and the rest is not all that relevant any more, so in theend I just decided to remove the file completely.Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Acked-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt; (powerpc)Acked-by: Helge Deller &lt;deller@gmx.de&gt; # pariscSigned-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux-6.15/arch/m68k/Kconfig</description>
        <pubDate>Mon, 23 May 2022 19:59:02 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
</channel>
</rss>
