Linux M68K

• Date Index

• Re: [PATCH 09/21] riscv: dma-mapping: skip invalidation before bidirectional DMA, (continued)
  • Re: [PATCH 09/21] riscv: dma-mapping: skip invalidation before bidirectional DMA, Conor Dooley
  • Re: [PATCH 09/21] riscv: dma-mapping: skip invalidation before bidirectional DMA, Lad, Prabhakar
  • Re: [PATCH 09/21] riscv: dma-mapping: skip invalidation before bidirectional DMA, Palmer Dabbelt
  • Re: [PATCH 09/21] riscv: dma-mapping: skip invalidation before bidirectional DMA, Guo Ren
    • Re: [PATCH 09/21] riscv: dma-mapping: skip invalidation before bidirectional DMA, Arnd Bergmann
      • Re: [PATCH 09/21] riscv: dma-mapping: skip invalidation before bidirectional DMA, Guo Ren
        • Re: [PATCH 09/21] riscv: dma-mapping: skip invalidation before bidirectional DMA, Arnd Bergmann
  • [PATCH 10/21] csky: dma-mapping: skip invalidating before DMA from device, Arnd Bergmann
    • Re: [PATCH 10/21] csky: dma-mapping: skip invalidating before DMA from device, Guo Ren
  • [PATCH 11/21] mips: dma-mapping: skip invalidating before bidirectional DMA, Arnd Bergmann
  • [PATCH 12/21] mips: dma-mapping: split out cache operation logic, Arnd Bergmann
  • [PATCH 13/21] arc: dma-mapping: skip invalidating before bidirectional DMA, Arnd Bergmann
    • Re: [PATCH 13/21] arc: dma-mapping: skip invalidating before bidirectional DMA, Vineet Gupta
      • Re: [PATCH 13/21] arc: dma-mapping: skip invalidating before bidirectional DMA, Shahab Vahedi
      • Re: [PATCH 13/21] arc: dma-mapping: skip invalidating before bidirectional DMA, Shahab Vahedi
  • [PATCH 14/21] parisc: dma-mapping: use regular flush/invalidate ops, Arnd Bergmann
  • [PATCH 15/21] ARM: dma-mapping: always invalidate WT caches before DMA, Arnd Bergmann
    • Re: [PATCH 15/21] ARM: dma-mapping: always invalidate WT caches before DMA, Linus Walleij
    • Re: [PATCH 15/21] ARM: dma-mapping: always invalidate WT caches before DMA, Russell King (Oracle)
      • Re: [PATCH 15/21] ARM: dma-mapping: always invalidate WT caches before DMA, Russell King (Oracle)
        • Re: [PATCH 15/21] ARM: dma-mapping: always invalidate WT caches before DMA, Arnd Bergmann
          • Re: [PATCH 15/21] ARM: dma-mapping: always invalidate WT caches before DMA, Russell King (Oracle)
            • Re: [PATCH 15/21] ARM: dma-mapping: always invalidate WT caches before DMA, Arnd Bergmann
  • [PATCH 16/21] ARM: dma-mapping: bring back dmac_{clean,inv}_range, Arnd Bergmann
    • Re: [PATCH 16/21] ARM: dma-mapping: bring back dmac_{clean,inv}_range, Russell King (Oracle)
  • [PATCH 17/21] ARM: dma-mapping: use arch_sync_dma_for_{device,cpu}() internally, Arnd Bergmann
    • Re: [PATCH 17/21] ARM: dma-mapping: use arch_sync_dma_for_{device,cpu}() internally, Linus Walleij
      • Re: [PATCH 17/21] ARM: dma-mapping: use arch_sync_dma_for_{device,cpu}() internally, Arnd Bergmann
  • [PATCH 18/21] ARM: drop SMP support for ARM11MPCore, Arnd Bergmann
    • Re: [PATCH 18/21] ARM: drop SMP support for ARM11MPCore, Neil Armstrong
      • Re: [PATCH 18/21] ARM: drop SMP support for ARM11MPCore, Arnd Bergmann
        • Re: [PATCH 18/21] ARM: drop SMP support for ARM11MPCore, Neil Armstrong
    • Re: [PATCH 18/21] ARM: drop SMP support for ARM11MPCore, Linus Walleij
    • Re: [PATCH 18/21] ARM: drop SMP support for ARM11MPCore, Ard Biesheuvel
    • Re: [PATCH 18/21] ARM: drop SMP support for ARM11MPCore, Catalin Marinas
  • [PATCH 19/21] ARM: dma-mapping: use generic form of arch_sync_dma_* helpers, Arnd Bergmann
  • [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Arnd Bergmann
    • Re: [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Robin Murphy
      • Re: [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Arnd Bergmann
        • Re: [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Robin Murphy
          • Re: [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Arnd Bergmann
    • Re: [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Russell King (Oracle)
      • Re: [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Arnd Bergmann
        • Re: [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Russell King (Oracle)
    • Re: [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Geert Uytterhoeven
      • Re: [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper, Christoph Hellwig
  • [PATCH 21/21] dma-mapping: replace custom code with generic implementation, Arnd Bergmann
    • Re: [PATCH 21/21] dma-mapping: replace custom code with generic implementation, Christoph Hellwig
      • Re: [PATCH 21/21] dma-mapping: replace custom code with generic implementation, Arnd Bergmann
    • Re: [PATCH 21/21] dma-mapping: replace custom code with generic implementation, Lad, Prabhakar
    • RE: [PATCH 21/21] dma-mapping: replace custom code with generic implementation, Biju Das
      • Re: [PATCH 21/21] dma-mapping: replace custom code with generic implementation, Arnd Bergmann
        • Re: [PATCH 21/21] dma-mapping: replace custom code with generic implementation, Geert Uytterhoeven
  • Re: [PATCH 00/21] dma-mapping: unify support for cache flushes, Catalin Marinas
    • Re: [PATCH 00/21] dma-mapping: unify support for cache flushes, Arnd Bergmann
  • Re: [PATCH 00/21] dma-mapping: unify support for cache flushes, Lad, Prabhakar
• [RFC PATCH v3] nubus: Don't list slot resources by default, Finn Thain
  • Re: [RFC PATCH v3] nubus: Don't list slot resources by default, Brad Boyer
    • Re: [RFC PATCH v3] nubus: Don't list slot resources by default, Finn Thain
      • Re: [RFC PATCH v3] nubus: Don't list slot resources by default, Brad Boyer
• [PATCH v3 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v3 01/14] arm: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
    • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Kefeng Wang
    • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Justin Forbes
      • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
        • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Justin Forbes
          • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Catalin Marinas
            • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Andrew Morton
              • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Catalin Marinas
                • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Justin Forbes
              • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Justin Forbes
                • Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Catalin Marinas
  • [PATCH v3 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
    • Re: [PATCH v3 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text, Kefeng Wang
  • [PATCH v3 04/14] csky: drop ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v3 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER, Mike Rapoport
    • Re: [PATCH v3 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER, Kefeng Wang
      • Re: [PATCH v3 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v3 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v3 07/14] nios2: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v3 08/14] nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v3 09/14] powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v3 10/14] powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v3 11/14] sh: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v3 12/14] sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v3 13/14] sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v3 14/14] xtensa: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
• [PATCH v2 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v2 01/14] arm: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v2 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v2 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
    • Re: [PATCH v2 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text, Zi Yan
  • [PATCH v2 04/14] csky: drop ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v2 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v2 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v2 07/14] nios2: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v2 08/14] nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v2 09/14] powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v2 10/14] powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v2 11/14] sh: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
    • Re: [PATCH v2 11/14] sh: reword ARCH_FORCE_MAX_ORDER prompt and help text, Zi Yan
  • [PATCH v2 12/14] sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH v2 13/14] sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH v2 14/14] xtensa: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • Re: [PATCH v2 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER, Zi Yan
    • Re: [PATCH v2 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER, Mike Rapoport
• [PATCH v4] Kconfig: introduce HAS_IOPORT option and select it as necessary, Niklas Schnelle
  • Re: [PATCH v4] Kconfig: introduce HAS_IOPORT option and select it as necessary, Niklas Schnelle
    • Re: [PATCH v4] Kconfig: introduce HAS_IOPORT option and select it as necessary, H. Peter Anvin
      • Re: [PATCH v4] Kconfig: introduce HAS_IOPORT option and select it as necessary, Arnd Bergmann
        • RE: [PATCH v4] Kconfig: introduce HAS_IOPORT option and select it as necessary, David Laight
          • Re: [PATCH v4] Kconfig: introduce HAS_IOPORT option and select it as necessary, Geert Uytterhoeven
            • RE: [PATCH v4] Kconfig: introduce HAS_IOPORT option and select it as necessary, David Laight
    • Re: [PATCH v4] Kconfig: introduce HAS_IOPORT option and select it as necessary, Arnd Bergmann
• [PATCH] m68k: Pass a pointer to virt_to_pfn() virt_to_page(), Linus Walleij
  • Re: [PATCH] m68k: Pass a pointer to virt_to_pfn() virt_to_page(), Andreas Schwab
    • Re: [PATCH] m68k: Pass a pointer to virt_to_pfn() virt_to_page(), Linus Walleij
• [PATCH 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH 01/14] arm: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
    • Re: [PATCH 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Catalin Marinas
      • Re: [PATCH 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
        • Re: [PATCH 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, Zi Yan
    • Re: [PATCH 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, kernel test robot
    • Re: [PATCH 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER, kernel test robot
  • [PATCH 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
    • Re: [PATCH 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text, Catalin Marinas
  • [PATCH 04/14] csky: drop ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
    • Re: [PATCH 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text, Geert Uytterhoeven
  • [PATCH 07/14] nios2: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH 08/14] nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH 09/14] powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH 10/14] powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH 11/14] sh: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH 12/14] sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER, Mike Rapoport
  • [PATCH 13/14] sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
  • [PATCH 14/14] xtensa: reword ARCH_FORCE_MAX_ORDER prompt and help text, Mike Rapoport
    • Re: [PATCH 14/14] xtensa: reword ARCH_FORCE_MAX_ORDER prompt and help text, Max Filippov
  • Re: [PATCH 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER, Kirill A. Shutemov
• [PATCH v2] nubus: Don't list card resources by default, Finn Thain
  • Re: [PATCH v2] nubus: Don't list card resources by default, Geert Uytterhoeven
    • Re: [PATCH v2] nubus: Don't list card resources by default, Finn Thain
      • Re: [PATCH v2] nubus: Don't list card resources by default, Brad Boyer
        • Re: [PATCH v2] nubus: Don't list card resources by default, Finn Thain
          • Re: [PATCH v2] nubus: Don't list card resources by default, Geert Uytterhoeven
            • Re: [PATCH v2] nubus: Don't list card resources by default, Brad Boyer
              • Re: [PATCH v2] nubus: Don't list card resources by default, Geert Uytterhoeven
          • Re: [PATCH v2] nubus: Don't list card resources by default, Brad Boyer
            • Re: [PATCH v2] nubus: Don't list card resources by default, Finn Thain
  • Re: [PATCH v2] nubus: Don't list card resources by default, Andreas Schwab
    • Re: [PATCH v2] nubus: Don't list card resources by default, Geert Uytterhoeven
      • Re: [PATCH v2] nubus: Don't list card resources by default, Finn Thain
        • Re: [PATCH v2] nubus: Don't list card resources by default, Geert Uytterhoeven
• Re: gdb failure: "core file format not supported", Finn Thain
  • Re: gdb failure: "core file format not supported", Finn Thain
    • Re: gdb failure: "core file format not supported", Geert Uytterhoeven
      • Re: gdb failure: "core file format not supported", Finn Thain
• [PATCH] nubus: Avoid scanning "private" card resources, Finn Thain
  • Re: [PATCH] nubus: Avoid scanning "private" card resources, Finn Thain
• [PATCH] nubus: Remove proc entries before adding them, Finn Thain
  • Re: [PATCH] nubus: Remove proc entries before adding them, Geert Uytterhoeven
• [geert-m68k:for-next] BUILD SUCCESS fda1941b8eab786112afe91088fa0a1ed4880360, kernel test robot
• [geert-m68k:master] BUILD SUCCESS b55f773e598a93232307dc61278cdf081adad7fa, kernel test robot
• [PATCH] nvme-tcp: fix nvme_tcp_term_pdu to match spec, Caleb Sander
  • Re: [PATCH] nvme-tcp: fix nvme_tcp_term_pdu to match spec, Sagi Grimberg
  • Re: [PATCH] nvme-tcp: fix nvme_tcp_term_pdu to match spec, Christoph Hellwig
• [PATCH] m68k: Kconfig.machine: remove obsolete configs ROMBASE and ROMSIZE, Lukas Bulwahn
  • Re: [PATCH] m68k: Kconfig.machine: remove obsolete configs ROMBASE and ROMSIZE, Geert Uytterhoeven
  • Re: [PATCH] m68k: Kconfig.machine: remove obsolete configs ROMBASE and ROMSIZE, Greg Ungerer
• [PATCH] m68k: remove obsolete config NO_KERNEL_MSG, Lukas Bulwahn
  • Re: [PATCH] m68k: remove obsolete config NO_KERNEL_MSG, Geert Uytterhoeven
• [PATCH] nvme-tcp: Fix implicit padding in struct nvme_tcp_term_pdu, Geert Uytterhoeven
  • Re: [PATCH] nvme-tcp: Fix implicit padding in struct nvme_tcp_term_pdu, Caleb Sander
    • Re: [PATCH] nvme-tcp: Fix implicit padding in struct nvme_tcp_term_pdu, Geert Uytterhoeven
• [PATCH AUTOSEL 4.14 4/9] m68k: Only force 030 bus error if PC not in exception table, Sasha Levin
• [PATCH AUTOSEL 4.19 4/9] m68k: Only force 030 bus error if PC not in exception table, Sasha Levin
• [PATCH AUTOSEL 5.4 04/12] m68k: Only force 030 bus error if PC not in exception table, Sasha Levin
• [PATCH AUTOSEL 5.15 06/17] m68k: Only force 030 bus error if PC not in exception table, Sasha Levin
• [PATCH AUTOSEL 5.10 05/15] m68k: Only force 030 bus error if PC not in exception table, Sasha Levin
• [PATCH AUTOSEL 6.1 07/29] m68k: Only force 030 bus error if PC not in exception table, Sasha Levin
• [PATCH AUTOSEL 6.1 06/29] m68k: mm: Fix systems with memory at end of 32-bit address space, Sasha Levin
• [PATCH AUTOSEL 6.2 07/30] m68k: Only force 030 bus error if PC not in exception table, Sasha Levin
• [PATCH AUTOSEL 6.2 06/30] m68k: mm: Fix systems with memory at end of 32-bit address space, Sasha Levin
• Re: [PATCH] drivers/mmc/core/bus: Delete redundant match function, Uwe Kleine-König
• [PATCH v1] nubus: Remove redunant driver match function, Lizhe
  • Re: [PATCH v1] nubus: Remove redunant driver match function, Finn Thain
    • Message not available
      • Re: [PATCH v1] nubus: Remove redunant driver match function, Uwe Kleine-König
        • Re: [PATCH v1] nubus: Remove redunant driver match function, Finn Thain
          • Re: [PATCH v1] nubus: Remove redunant driver match function, Uwe Kleine-König
    • Message not available
      • Re:Re: [PATCH v1] nubus: Remove redunant driver match function, Finn Thain
• [PATCH v4 14/36] m68k: Implement the new page table range API, Matthew Wilcox (Oracle)
  • Re: [PATCH v4 14/36] m68k: Implement the new page table range API, Geert Uytterhoeven
    • Re: [PATCH v4 14/36] m68k: Implement the new page table range API, Geert Uytterhoeven
  • Re: [PATCH v4 14/36] m68k: Implement the new page table range API, Mike Rapoport
• [PATCH v3 01/38] Kconfig: introduce HAS_IOPORT option and select it as necessary, Niklas Schnelle
  • Re: [PATCH v3 01/38] Kconfig: introduce HAS_IOPORT option and select it as necessary, Johannes Berg
    • Re: [PATCH v3 01/38] Kconfig: introduce HAS_IOPORT option and select it as necessary, Niklas Schnelle
  • Re: [PATCH v3 01/38] Kconfig: introduce HAS_IOPORT option and select it as necessary, Geert Uytterhoeven
  • Re: [PATCH v3 01/38] Kconfig: introduce HAS_IOPORT option and select it as necessary, Arnd Bergmann
    • Re: [PATCH v3 01/38] Kconfig: introduce HAS_IOPORT option and select it as necessary, Niklas Schnelle
  • Re: [PATCH v3 01/38] Kconfig: introduce HAS_IOPORT option and select it as necessary, Niklas Schnelle
• [PATCH] nubus: Partially revert proc_create_single_data() conversion, Finn Thain
  • Re: [PATCH] nubus: Partially revert proc_create_single_data() conversion, Geert Uytterhoeven
• [geert-m68k:master] BUILD SUCCESS 28230bb22d4ea73c91d7e934dc2f162f931733ae, kernel test robot
• [PATCH] nubus: Drop noop match function, Uwe Kleine-König
  • Re: [PATCH] nubus: Drop noop match function, Finn Thain
    • Re: [PATCH] nubus: Drop noop match function, Geert Uytterhoeven
• [GIT PULL] m68k fixes for v6.3, Geert Uytterhoeven
  • Re: [GIT PULL] m68k fixes for v6.3, pr-tracker-bot
• [PATCH v4 3/4] arch/*/io.h: remove ioremap_uc in some architectures, Baoquan He
  • Re: [PATCH v4 3/4] arch/*/io.h: remove ioremap_uc in some architectures, Thomas Bogendoerfer
    • Re: [PATCH v4 3/4] arch/*/io.h: remove ioremap_uc in some architectures, Baoquan He
      • Re: [PATCH v4 3/4] arch/*/io.h: remove ioremap_uc in some architectures, Helge Deller
  • Re: [PATCH v4 3/4] arch/*/io.h: remove ioremap_uc in some architectures, Michael Ellerman
• [geert-m68k:master] BUILD SUCCESS 513138a14063760ef611f18ba76c5c7915ff8cdd, kernel test robot
• [geert-m68k:for-v6.3] BUILD SUCCESS e36a82bebbf7da814530d5a179bef9df5934b717, kernel test robot
• [PATCH] m68k: defconfig: Update defconfigs for v6.3-rc1, Geert Uytterhoeven
• [PATCH v5 00/26] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 01/26] alpha: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 02/26] arm64: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 03/26] arm: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 04/26] ia64: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 05/26] m68k: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 06/26] microblaze: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 07/26] mips: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 08/26] parisc: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 09/26] powerpc: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 10/26] sparc: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 11/26] xtensa: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 12/26] riscv: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v5 12/26] riscv: Remove COMMAND_LINE_SIZE from uapi, Palmer Dabbelt
  • [PATCH v5 13/26] asm-generic: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v5 14/26] alpha: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
    • Re: [PATCH v5 14/26] alpha: Remove empty <uapi/asm/setup.h>, Maciej W. Rozycki
  • [PATCH v5 15/26] arc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 16/26] m68k: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 17/26] arm64: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 18/26] microblaze: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 19/26] sparc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 20/26] parisc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 21/26] x86: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 22/26] xtensa: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 23/26] powerpc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 24/26] mips: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 25/26] s390: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v5 26/26] riscv: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • Re: [PATCH v5 00/26] Remove COMMAND_LINE_SIZE from uapi, Philippe Mathieu-Daudé
  • Re: [PATCH v5 00/26] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
• [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures, Baoquan He
  • Re: [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures, Michael Ellerman
    • Re: [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures, Geert Uytterhoeven
      • Re: [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures, Arnd Bergmann
        • Re: [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures, Michael Ellerman
          • Re: [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures, Baoquan He
            • Re: [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures, Arnd Bergmann
• [PATCH v4 00/24] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 01/24] alpha: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 02/24] arm64: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 03/24] arm: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 04/24] ia64: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 05/24] m68k: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 06/24] microblaze: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 07/24] mips: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 08/24] parisc: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 09/24] powerpc: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 10/24] sparc: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 11/24] xtensa: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 12/24] asm-generic: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • Re: [PATCH v4 00/24] Remove COMMAND_LINE_SIZE from uapi, Geert Uytterhoeven
    • Re: [PATCH v4 00/24] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
      • Re: [PATCH v4 00/24] Remove COMMAND_LINE_SIZE from uapi, Geert Uytterhoeven
        • Re: [PATCH v4 00/24] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v4 13/24] alpha: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 14/24] arc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 15/24] m68k: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 16/24] arm64: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 17/24] microblaze: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 18/24] sparc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 19/24] parisc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 20/24] x86: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 21/24] xtensa: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 22/24] powerpc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 24/24] s390: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v4 23/24] mips: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • Re: [PATCH v4 00/24] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v4 00/24] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
• [PATCH v5 01/17] asm-generic/iomap.h: remove ARCH_HAS_IOREMAP_xx macros, Baoquan He
  • Re: [PATCH v5 01/17] asm-generic/iomap.h: remove ARCH_HAS_IOREMAP_xx macros, Edward Cree
    • Re: [PATCH v5 01/17] asm-generic/iomap.h: remove ARCH_HAS_IOREMAP_xx macros, Matthew Wilcox
      • Re: [PATCH v5 01/17] asm-generic/iomap.h: remove ARCH_HAS_IOREMAP_xx macros, Baoquan He
• [PATCH v2] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Michael Schmitz
  • Re: [PATCH v2] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Geert Uytterhoeven
    • Re: [PATCH v2] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Michael Schmitz
      • Re: [PATCH v2] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Geert Uytterhoeven
        • Re: [PATCH v2] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Michael Schmitz
• [PATCH v3 13/34] m68k: Implement the new page table range API, Matthew Wilcox (Oracle)
  • Re: [PATCH v3 13/34] m68k: Implement the new page table range API, Geert Uytterhoeven
    • Re: [PATCH v3 13/34] m68k: Implement the new page table range API, Matthew Wilcox
      • Re: [PATCH v3 13/34] m68k: Implement the new page table range API, Geert Uytterhoeven
      • Re: [PATCH v3 13/34] m68k: Implement the new page table range API, Michael Schmitz
        • Re: [PATCH v3 13/34] m68k: Implement the new page table range API, Geert Uytterhoeven
          • Re: [PATCH v3 13/34] m68k: Implement the new page table range API, Michael Schmitz
• [PATCH] MAINTAINERS: drop uclinux.org, Randy Dunlap
  • Re: [PATCH] MAINTAINERS: drop uclinux.org, Greg Ungerer
  • Re: [PATCH] MAINTAINERS: drop uclinux.org, Greg Ungerer
• [PATCH v7 13/41] mm: Make pte_mkwrite() take a VMA, Rick Edgecombe
  • Re: [PATCH v7 13/41] mm: Make pte_mkwrite() take a VMA, Christophe Leroy
    • Re: [PATCH v7 13/41] mm: Make pte_mkwrite() take a VMA, David Hildenbrand
  • Re: [PATCH v7 13/41] mm: Make pte_mkwrite() take a VMA, Borislav Petkov
• [PATCH] m68k: mm: Move initrd phys_to_virt handling after paging_init(), Geert Uytterhoeven
  • Re: [PATCH] m68k: mm: Move initrd phys_to_virt handling after paging_init(), Finn Thain
    • Re: [PATCH] m68k: mm: Move initrd phys_to_virt handling after paging_init(), Geert Uytterhoeven
      • Re: [PATCH] m68k: mm: Move initrd phys_to_virt handling after paging_init(), Finn Thain
• [PATCH v2 12/30] m68k: Implement the new page table range API, Matthew Wilcox (Oracle)
• [PATCH] SUNRPC: Ensure test case arrays are properly terminated, Chuck Lever
  • Re: [PATCH] SUNRPC: Ensure test case arrays are properly terminated, Geert Uytterhoeven
• [PATCH] SUNRPC: Let Kunit tests run with some enctypes compiled out, Chuck Lever
  • Re: [PATCH] SUNRPC: Let Kunit tests run with some enctypes compiled out, Geert Uytterhoeven
• [PATCH] kunit: tool: Add support for m68k under QEMU, Geert Uytterhoeven
  • Re: [PATCH] kunit: tool: Add support for m68k under QEMU, David Gow
• [git pull] m68knommu changes for v6.3, Greg Ungerer
  • Re: [git pull] m68knommu changes for v6.3, pr-tracker-bot
• [PATCH AUTOSEL 6.1 26/49] m68k: Check syscall_trace_enter() return code, Sasha Levin
• [PATCH AUTOSEL 4.14 10/11] m68k: Check syscall_trace_enter() return code, Sasha Levin
• [PATCH AUTOSEL 4.19 11/13] m68k: Check syscall_trace_enter() return code, Sasha Levin
• [PATCH AUTOSEL 5.4 13/19] m68k: Check syscall_trace_enter() return code, Sasha Levin
• [PATCH AUTOSEL 5.10 19/27] m68k: Check syscall_trace_enter() return code, Sasha Levin
• [PATCH AUTOSEL 5.15 21/36] m68k: Check syscall_trace_enter() return code, Sasha Levin
• [PATCH AUTOSEL 6.2 28/53] m68k: Check syscall_trace_enter() return code, Sasha Levin
• Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Geert Uytterhoeven
  • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Chuck Lever III
    • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Geert Uytterhoeven
      • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Chuck Lever III
        • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Geert Uytterhoeven
          • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Chuck Lever III
          • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Geert Uytterhoeven
            • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Chuck Lever III
              • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Geert Uytterhoeven
        • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Andreas Schwab
          • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Michael Schmitz
            • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Andreas Schwab
              • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Michael Schmitz
        • Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements, Eero Tamminen
• [PATCH] m68k: fix for systems with memory at end of 32-bit address space, Kars de Jong
  • Re: [PATCH] m68k: fix for systems with memory at end of 32-bit address space, Geert Uytterhoeven
    • Re: [PATCH] m68k: fix for systems with memory at end of 32-bit address space, Kars de Jong
      • Re: [PATCH] m68k: fix for systems with memory at end of 32-bit address space, Kars de Jong
        • Re: [PATCH] m68k: fix for systems with memory at end of 32-bit address space, Geert Uytterhoeven
          • Re: [PATCH] m68k: fix for systems with memory at end of 32-bit address space, Michael Schmitz
  • Re: [PATCH] m68k: fix for systems with memory at end of 32-bit address space, Kars de Jong
    • Re: [PATCH] m68k: fix for systems with memory at end of 32-bit address space, Geert Uytterhoeven
• [PATCH RFC v1] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Michael Schmitz
  • Re: [PATCH RFC v1] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Eero Tamminen
    • Re: [PATCH RFC v1] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Michael Schmitz
  • Re: [PATCH RFC v1] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Geert Uytterhoeven
    • Re: [PATCH RFC v1] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Michael Schmitz
      • Re: [PATCH RFC v1] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Geert Uytterhoeven
        • Re: [PATCH RFC v1] m68k: kernel/traps.c - only force 030 bus error if PC not in exception table, Michael Schmitz
• Booting 6.2.0-rc8 on HP 9000/425t - all memory is reserved, Kars de Jong
• Kernel versions 6.x don't boot on Amiga 4000, John Paul Adrian Glaubitz
  • Re: Kernel versions 6.x don't boot on Amiga 4000, Geert Uytterhoeven
    • Re: Kernel versions 6.x don't boot on Amiga 4000, John Paul Adrian Glaubitz
      • Re: Kernel versions 6.x don't boot on Amiga 4000, Michael Schmitz
        • Re: Kernel versions 6.x don't boot on Amiga 4000, John Paul Adrian Glaubitz
          • Re: Kernel versions 6.x don't boot on Amiga 4000, Michael Schmitz
            • Re: Kernel versions 6.x don't boot on Amiga 4000, Michael Schmitz
      • Re: Kernel versions 6.x don't boot on Amiga 4000, Geert Uytterhoeven
        • Re: Kernel versions 6.x don't boot on Amiga 4000, Geert Uytterhoeven
          • Re: Kernel versions 6.x don't boot on Amiga 4000, Michael Schmitz
            • Re: Kernel versions 6.x don't boot on Amiga 4000, Finn Thain
              • Re: Kernel versions 6.x don't boot on Amiga 4000, Michael Schmitz
                • Re: Kernel versions 6.x don't boot on Amiga 4000, Eero Tamminen
                  • Re: Kernel versions 6.x don't boot on Amiga 4000, Michael Schmitz
          • Re: Kernel versions 6.x don't boot on Amiga 4000, Michael Schmitz
            • Re: Kernel versions 6.x don't boot on Amiga 4000, Finn Thain
              • Re: Kernel versions 6.x don't boot on Amiga 4000, Finn Thain
              • Re: Kernel versions 6.x don't boot on Amiga 4000, Geert Uytterhoeven
                • Re: Kernel versions 6.x don't boot on Amiga 4000, Michael Schmitz
                  • Re: Kernel versions 6.x don't boot on Amiga 4000, Mike Rapoport
                    • Re: Kernel versions 6.x don't boot on Amiga 4000, Geert Uytterhoeven
                      • Re: Kernel versions 6.x don't boot on Amiga 4000, Mike Rapoport
• [geert-m68k:m68k-v6.2] BUILD SUCCESS b1b5209c1e80a9c9912dfe38986fabbc71a2904e, kernel test robot
• [geert-m68k:master] BUILD SUCCESS 0fcf6b2d92cbb554127e342ca27adefa569ff63f, kernel test robot
• [GIT PULL] m68k updates for v6.3, Geert Uytterhoeven
  • Re: [GIT PULL] m68k updates for v6.3, pr-tracker-bot
• [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA, Rick Edgecombe
  • Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA, Kees Cook
  • Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA, Michael Ellerman
    • Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA, Edgecombe, Rick P
  • Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA, David Hildenbrand
    • Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA, Edgecombe, Rick P
  • Re: [PATCH v6 13/41] mm: Make pte_mkwrite() take a VMA, Deepak Gupta
• [PATCH 15/17] m68k: Implement the new page table range API, Matthew Wilcox (Oracle)
  • Re: [PATCH 15/17] m68k: Implement the new page table range API, Michael Schmitz
    • Re: [PATCH 15/17] m68k: Implement the new page table range API, Matthew Wilcox
      • Re: [PATCH 15/17] m68k: Implement the new page table range API, Geert Uytterhoeven
      • Re: [PATCH 15/17] m68k: Implement the new page table range API, Michael Schmitz
• [PATCH 0/2] fixups for generic implementation of pfn_valid(), Mike Rapoport
  • [PATCH 1/2] m68k/nommu: add missing definition of ARCH_PFN_OFFSET, Mike Rapoport
    • Re: [PATCH 1/2] m68k/nommu: add missing definition of ARCH_PFN_OFFSET, Greg Ungerer
    • Re: [PATCH 1/2] m68k/nommu: add missing definition of ARCH_PFN_OFFSET, David Hildenbrand
  • [PATCH 2/2] sh: initialize max_mapnr, Mike Rapoport
    • Re: [PATCH 2/2] sh: initialize max_mapnr, John Paul Adrian Glaubitz
    • Re: [PATCH 2/2] sh: initialize max_mapnr, David Hildenbrand
• [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v3 01/24] alpha: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v3 01/24] alpha: Remove COMMAND_LINE_SIZE from uapi, Philippe Mathieu-Daudé
  • [PATCH v3 02/24] arm64: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v3 02/24] arm64: Remove COMMAND_LINE_SIZE from uapi, Catalin Marinas
  • [PATCH v3 03/24] arm: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v3 03/24] arm: Remove COMMAND_LINE_SIZE from uapi, Russell King (Oracle)
      • Re: [PATCH v3 03/24] arm: Remove COMMAND_LINE_SIZE from uapi, Arnd Bergmann
        • Re: [PATCH v3 03/24] arm: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
          • Re: [PATCH v3 03/24] arm: Remove COMMAND_LINE_SIZE from uapi, Arnd Bergmann
            • Re: [PATCH v3 03/24] arm: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
            • Re: [PATCH v3 03/24] arm: Remove COMMAND_LINE_SIZE from uapi, Palmer Dabbelt
  • [PATCH v3 04/24] ia64: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v3 05/24] m68k: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v3 05/24] m68k: Remove COMMAND_LINE_SIZE from uapi, Geert Uytterhoeven
  • [PATCH v3 06/24] microblaze: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v3 07/24] mips: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v3 07/24] mips: Remove COMMAND_LINE_SIZE from uapi, Philippe Mathieu-Daudé
  • [PATCH v3 08/24] parisc: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v3 08/24] parisc: Remove COMMAND_LINE_SIZE from uapi, Philippe Mathieu-Daudé
      • Re: [PATCH v3 08/24] parisc: Remove COMMAND_LINE_SIZE from uapi, Helge Deller
  • [PATCH v3 09/24] powerpc: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v3 09/24] powerpc: Remove COMMAND_LINE_SIZE from uapi, Michael Ellerman
  • [PATCH v3 10/24] sparc: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v3 10/24] sparc: Remove COMMAND_LINE_SIZE from uapi, Sergey Shtylyov
      • Re: [PATCH v3 10/24] sparc: Remove COMMAND_LINE_SIZE from uapi, WANG Xuerui
        • Re: [PATCH v3 10/24] sparc: Remove COMMAND_LINE_SIZE from uapi, Sergey Shtylyov
        • Re: [PATCH v3 10/24] sparc: Remove COMMAND_LINE_SIZE from uapi, John Paul Adrian Glaubitz
  • [PATCH v3 11/24] xtensa: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
    • Re: [PATCH v3 11/24] xtensa: Remove COMMAND_LINE_SIZE from uapi, Max Filippov
  • [PATCH v3 12/24] asm-generic: Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
  • [PATCH v3 13/24] alpha: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v3 14/24] arc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
    • Re: [PATCH v3 14/24] arc: Remove empty <uapi/asm/setup.h>, Philippe Mathieu-Daudé
  • [PATCH v3 15/24] m68k: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
    • Re: [PATCH v3 15/24] m68k: Remove empty <uapi/asm/setup.h>, Geert Uytterhoeven
  • [PATCH v3 16/24] arm64: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v3 17/24] microblaze: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v3 18/24] sparc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v3 19/24] parisc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
    • Re: [PATCH v3 19/24] parisc: Remove empty <uapi/asm/setup.h>, Philippe Mathieu-Daudé
      • Re: [PATCH v3 19/24] parisc: Remove empty <uapi/asm/setup.h>, Helge Deller
  • [PATCH v3 20/24] x86: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
    • Re: [PATCH v3 20/24] x86: Remove empty <uapi/asm/setup.h>, Philippe Mathieu-Daudé
  • [PATCH v3 21/24] xtensa: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
    • Re: [PATCH v3 21/24] xtensa: Remove empty <uapi/asm/setup.h>, Max Filippov
  • [PATCH v3 22/24] powerpc: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v3 23/24] mips: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
  • [PATCH v3 24/24] s390: Remove empty <uapi/asm/setup.h>, Alexandre Ghiti
    • Re: [PATCH v3 24/24] s390: Remove empty <uapi/asm/setup.h>, Heiko Carstens
    • Re: [PATCH v3 24/24] s390: Remove empty <uapi/asm/setup.h>, Philippe Mathieu-Daudé
  • Re: [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, Heiko Carstens
    • Re: [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, Geert Uytterhoeven
      • Re: [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, Heiko Carstens
        • Re: [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, Palmer Dabbelt
          • Re: [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
          • Re: [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, H. Peter Anvin
            • Re: [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
              • Re: [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, Arnd Bergmann
                • Re: [PATCH v3 00/24] Remove COMMAND_LINE_SIZE from uapi, Alexandre Ghiti
• [geert-m68k:for-v6.3] BUILD SUCCESS 1e5b5df65af99013b4d31607ddb3ca5731dbe44d, kernel test robot
• [geert-m68k:master] BUILD SUCCESS b997879e7c2e1205eaf3b546b4de696fe049cd9d, kernel test robot
• [PATCH] m68k: /proc/hardware depends on PROC_FS, Randy Dunlap
  • Re: [PATCH] m68k: /proc/hardware depends on PROC_FS, Geert Uytterhoeven
    • Re: [PATCH] m68k: /proc/hardware depends on PROC_FS, Randy Dunlap
• [PATCH] m68k: allow PM menu options for COMPILE_TEST, Randy Dunlap
  • Re: [PATCH] m68k: allow PM menu options for COMPILE_TEST, Geert Uytterhoeven
    • Re: [PATCH] m68k: allow PM menu options for COMPILE_TEST, Randy Dunlap
• [PATCH] input/misc: hp_sdc_rtc: mark an unused function as __maybe_unused, Randy Dunlap
  • Re: [PATCH] input/misc: hp_sdc_rtc: mark an unused function as __maybe_unused, Geert Uytterhoeven
    • Re: [PATCH] input/misc: hp_sdc_rtc: mark an unused function as __maybe_unused, Helge Deller
• [PATCH v4 00/18] gpiolib cleanups, Andy Shevchenko
  • [PATCH v4 01/18] ARM: orion/gpio: Use the right include, Andy Shevchenko
  • [PATCH v4 04/18] gpiolib: Make the legacy <linux/gpio.h> consumer-only, Andy Shevchenko
  • [PATCH v4 07/18] gpiolib: remove asm-generic/gpio.h, Andy Shevchenko
  • [PATCH v4 02/18] ARM: s3c24xx: Use the right include, Andy Shevchenko
    • Re: [PATCH v4 02/18] ARM: s3c24xx: Use the right include, Krzysztof Kozlowski
      • Re: [PATCH v4 02/18] ARM: s3c24xx: Use the right include, Andy Shevchenko
      • Re: [PATCH v4 02/18] ARM: s3c24xx: Use the right include, Linus Walleij
    • Re: [PATCH v4 02/18] ARM: s3c24xx: Use the right include, Krzysztof Kozlowski
  • [PATCH v4 06/18] gpiolib: coldfire: remove custom asm/gpio.h, Andy Shevchenko
  • [PATCH v4 17/18] gpiolib: Group forward declarations in consumer.h, Andy Shevchenko
    • Re: [PATCH v4 17/18] gpiolib: Group forward declarations in consumer.h, Linus Walleij
  • [PATCH v4 14/18] gpio: regmap: Add missing header(s), Andy Shevchenko
    • Re: [PATCH v4 14/18] gpio: regmap: Add missing header(s), Linus Walleij
  • [PATCH v4 09/18] gpiolib: remove legacy gpio_export(), Andy Shevchenko
  • [PATCH v4 11/18] gpiolib: split of_mm_gpio_chip out of linux/of_gpio.h, Andy Shevchenko
  • [PATCH v4 16/18] gpiolib: Deduplicate forward declarations in consumer.h, Andy Shevchenko
    • Re: [PATCH v4 16/18] gpiolib: Deduplicate forward declarations in consumer.h, Linus Walleij
  • [PATCH v4 08/18] gpiolib: remove gpio_set_debounce(), Andy Shevchenko
    • Re: [PATCH v4 08/18] gpiolib: remove gpio_set_debounce(), Dmitry Torokhov
  • [PATCH v4 05/18] gpiolib: remove empty asm/gpio.h files, Andy Shevchenko
  • [PATCH v4 03/18] hte: tegra-194: Use proper includes, Andy Shevchenko
    • Re: [PATCH v4 03/18] hte: tegra-194: Use proper includes, Dipen Patel
  • [PATCH v4 10/18] gpiolib: split linux/gpio/driver.h out of linux/gpio.h, Andy Shevchenko
  • [PATCH v4 12/18] gpio: aggregator: Add missing header(s), Andy Shevchenko
    • Re: [PATCH v4 12/18] gpio: aggregator: Add missing header(s), Linus Walleij
  • [PATCH v4 15/18] gpiolib: Drop unused forward declaration from driver.h, Andy Shevchenko
  • [PATCH v4 13/18] gpio: reg: Add missing header(s), Andy Shevchenko
    • Re: [PATCH v4 13/18] gpio: reg: Add missing header(s), Linus Walleij
  • [PATCH v4 18/18] gpiolib: Clean up headers, Andy Shevchenko
    • Re: [PATCH v4 18/18] gpiolib: Clean up headers, Linus Walleij
  • Re: [PATCH v4 00/18] gpiolib cleanups, Bartosz Golaszewski
    • Re: [PATCH v4 00/18] gpiolib cleanups, Andy Shevchenko
• Re: API for setting multiple PTEs at once, Matthew Wilcox
  • Re: API for setting multiple PTEs at once, Alexandre Ghiti
    • Re: API for setting multiple PTEs at once, Yin, Fengwei
      • Re: API for setting multiple PTEs at once, Matthew Wilcox
  • Re: API for setting multiple PTEs at once, Alexandre Ghiti
    • Re: API for setting multiple PTEs at once, Rolf Eike Beer
• [PATCH v3 00/12] gpiolib cleanups, Andy Shevchenko
  • [PATCH v3 02/12] gpiolib: coldfire: remove custom asm/gpio.h, Andy Shevchenko
  • [PATCH v3 01/12] gpiolib: remove empty asm/gpio.h files, Andy Shevchenko
    • Re: [PATCH v3 01/12] gpiolib: remove empty asm/gpio.h files, Vincenzo Palazzo
  • [PATCH v3 03/12] gpiolib: remove asm-generic/gpio.h, Andy Shevchenko
  • [PATCH v3 05/12] gpiolib: remove legacy gpio_export, Andy Shevchenko
  • [PATCH v3 06/12] gpiolib: split linux/gpio/driver.h out of linux/gpio.h, Andy Shevchenko
    • Re: [PATCH v3 06/12] gpiolib: split linux/gpio/driver.h out of linux/gpio.h, Linus Walleij
      • Re: [PATCH v3 06/12] gpiolib: split linux/gpio/driver.h out of linux/gpio.h, Andy Shevchenko
        • Re: [PATCH v3 06/12] gpiolib: split linux/gpio/driver.h out of linux/gpio.h, Andy Shevchenko
          • Re: [PATCH v3 06/12] gpiolib: split linux/gpio/driver.h out of linux/gpio.h, Linus Walleij
    • Re: [PATCH v3 06/12] gpiolib: split linux/gpio/driver.h out of linux/gpio.h, Lee Jones
  • [PATCH v3 07/12] gpiolib: split of_mm_gpio_chip out of linux/of_gpio.h, Andy Shevchenko
  • [PATCH v3 10/12] gpiolib: Deduplicate forward declarations in consumer.h, Andy Shevchenko
  • [PATCH v3 11/12] gpiolib: Group forward declarations in consumer.h, Andy Shevchenko
  • [PATCH v3 09/12] gpiolib: Drop unused forward declaration from driver.h, Andy Shevchenko
  • [PATCH v3 08/12] gpio: aggregator: Add missing header(s), Andy Shevchenko
    • Re: [PATCH v3 08/12] gpio: aggregator: Add missing header(s), Geert Uytterhoeven
  • [PATCH v3 12/12] gpiolib: Clean up headers, Andy Shevchenko
  • [PATCH v3 04/12] gpiolib: remove gpio_set_debounce, Andy Shevchenko
    • Re: [PATCH v3 04/12] gpiolib: remove gpio_set_debounce, Dmitry Torokhov
      • Re: [PATCH v3 04/12] gpiolib: remove gpio_set_debounce, Andy Shevchenko
• [geert-m68k:master] BUILD SUCCESS 29f28f8b826d7684e6b05df0f5de38dfcceb77c4, kernel test robot
• m68k assembly question: jsr vs. bsr, John Paul Adrian Glaubitz
  • Re: m68k assembly question: jsr vs. bsr, Geert Uytterhoeven
    • Re: m68k assembly question: jsr vs. bsr, Andreas Schwab
• [RFC][PATCHSET] VM_FAULT_RETRY fixes, Al Viro
  • [PATCH 01/10] alpha: fix livelock in uaccess, Al Viro
    • Re: [PATCH 01/10] alpha: fix livelock in uaccess, patchwork-bot+linux-riscv
  • [PATCH 02/10] hexagon: fix livelock in uaccess, Al Viro
    • RE: [PATCH 02/10] hexagon: fix livelock in uaccess, Brian Cain
  • [PATCH 03/10] ia64: fix livelock in uaccess, Al Viro
  • [PATCH 04/10] m68k: fix livelock in uaccess, Al Viro
    • Re: [PATCH 04/10] m68k: fix livelock in uaccess, Finn Thain
      • Re: [PATCH 04/10] m68k: fix livelock in uaccess, Linus Torvalds
        • Re: [PATCH 04/10] m68k: fix livelock in uaccess, Finn Thain
      • Re: [PATCH 04/10] m68k: fix livelock in uaccess, Al Viro
        • Re: [PATCH 04/10] m68k: fix livelock in uaccess, Linus Torvalds
    • Re: [PATCH 04/10] m68k: fix livelock in uaccess, Geert Uytterhoeven
  • [PATCH 05/10] microblaze: fix livelock in uaccess, Al Viro
  • [PATCH 06/10] nios2: fix livelock in uaccess, Al Viro
  • [PATCH 07/10] openrisc: fix livelock in uaccess, Al Viro
  • [PATCH 08/10] parisc: fix livelock in uaccess, Al Viro
    • Re: [PATCH 08/10] parisc: fix livelock in uaccess, Helge Deller
      • Re: [PATCH 08/10] parisc: fix livelock in uaccess, Al Viro
    • Re: [PATCH 08/10] parisc: fix livelock in uaccess, Guenter Roeck
      • Re: [PATCH 08/10] parisc: fix livelock in uaccess, Michael Schmitz
  • [PATCH 09/10] riscv: fix livelock in uaccess, Al Viro
    • Re: [PATCH 09/10] riscv: fix livelock in uaccess, Björn Töpel
    • Re: [PATCH 09/10] riscv: fix livelock in uaccess, Geert Uytterhoeven
  • [PATCH 10/10] sparc: fix livelock in uaccess, Al Viro
  • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Linus Torvalds
    • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Al Viro
      • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Linus Torvalds
        • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Al Viro
          • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Linus Torvalds
            • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Peter Xu
              • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Al Viro
                • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Al Viro
                • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Peter Xu
                  • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Al Viro
                    • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Al Viro
        • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Helge Deller
          • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Linus Torvalds
  • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Mark Rutland
    • Re: [RFC][PATCHSET] VM_FAULT_RETRY fixes, Geert Uytterhoeven
• [geert-m68k:master] BUILD SUCCESS 6aee36105369223c6859cc6cf042d262caa1068f, kernel test robot
• [geert-m68k:for-v6.3] BUILD SUCCESS be6c50d315f92071e481eacd1c0260cb4f7c325f, kernel test robot
• Re: stack smashing detected, Geert Uytterhoeven
  • <Possible follow-ups>
  • Re: stack smashing detected, Michael Schmitz
    • Message not available
      • Re: stack smashing detected, Michael Schmitz
        • Re: stack smashing detected, Geert Uytterhoeven
        • Message not available
          • Re: stack smashing detected, Michael Schmitz
        • Re: stack smashing detected, Michael Schmitz
          • Message not available
            • Re: stack smashing detected, Michael Schmitz
              • Re: stack smashing detected, Michael Schmitz
                • Message not available
                  • Message not available
                    • Message not available
                      • Message not available
                        • Message not available
                          • Message not available
                            • Message not available
                              • Message not available
                                • Message not available
                                • Message not available
                                • Message not available
                                • Message not available
                                • Message not available
                                • core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Andreas Schwab
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Michael Schmitz
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Michael Schmitz
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Michael Schmitz
                                • dash behaviour, was Re: core dump analysis, Finn Thain
                                • Re: dash behaviour, was Re: core dump analysis, Geert Uytterhoeven
                                • Re: dash behaviour, was Re: core dump analysis, Finn Thain
                                • Re: dash behaviour, was Re: core dump analysis, Geert Uytterhoeven
                                • Re: dash behaviour, was Re: core dump analysis, Michael Schmitz
                                • Re: dash behaviour, was Re: core dump analysis, Finn Thain
                                • Re: dash behaviour, was Re: core dump analysis, Michael Schmitz
                                • Re: dash behaviour, was Re: core dump analysis, Finn Thain
                                • Re: dash behaviour, was Re: core dump analysis, Michael Schmitz
                                • kernel behaviour, was Re: dash behaviour, Finn Thain
                                • Re: kernel behaviour, was Re: dash behaviour, Michael Schmitz
                                • Re: kernel behaviour, was Re: dash behaviour, Finn Thain
                                • Re: kernel behaviour, was Re: dash behaviour, Geert Uytterhoeven
                                • Re: core dump analysis, was Re: stack smashing detected, Geert Uytterhoeven
                                • Re: core dump analysis, was Re: stack smashing detected, Michael Schmitz
                                • instrumentation, was Re: core dump analysis, Finn Thain
                                • Re: instrumentation, was Re: core dump analysis, Michael Schmitz
                                • Re: instrumentation, was Re: core dump analysis, Finn Thain
                                • Re: instrumentation, was Re: core dump analysis, Geert Uytterhoeven
                                • Re: instrumentation, was Re: core dump analysis, Michael Schmitz
                                • Re: instrumentation, was Re: core dump analysis, Eero Tamminen
                                • Re: instrumentation, was Re: core dump analysis, Eero Tamminen
                                • Re: instrumentation, was Re: core dump analysis, Brad Boyer
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Michael Schmitz
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Michael Schmitz
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Michael Schmitz
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Michael Schmitz
                                • Re: core dump analysis, was Re: stack smashing detected, Finn Thain
                                • Re: core dump analysis, was Re: stack smashing detected, Michael Schmitz
                                • reliable reproducer, was Re: core dump analysis, Finn Thain
                                • Re: reliable reproducer, was Re: core dump analysis, Geert Uytterhoeven
                                • Re: reliable reproducer, was Re: core dump analysis, Finn Thain
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Finn Thain
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Finn Thain
                                • Re: reliable reproducer, was Re: core dump analysis, Finn Thain
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Finn Thain
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Finn Thain
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Finn Thain
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Andreas Schwab
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Andreas Schwab
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Andreas Schwab
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Andreas Schwab
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Andreas Schwab
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz
                                • Re: reliable reproducer, was Re: core dump analysis, Andreas Schwab
                                • Re: reliable reproducer, was Re: core dump analysis, Michael Schmitz