Re: [PATCH 2/6] sh: remove duplicate ioread/iowrite helpers

Hello Geert, On Sun, 2025-06-08 at 11:39 +0200, Geert Uytterhoeven wrote: > Hi Adrian, > > On Sat, 7 Jun 2025 at 14:08, John Paul Adrian Glaubitz > wrote: > > On Sat, 2025-03-15 at 11:59 +0100, Arnd Bergmann wrote: > > > From: Arnd Bergmann > > > > > > The ioread/iowrite functions on sh only d

Re: [PATCH 2/6] sh: remove duplicate ioread/iowrite helpers

Hi Adrian, On Sat, 7 Jun 2025 at 14:08, John Paul Adrian Glaubitz wrote: > On Sat, 2025-03-15 at 11:59 +0100, Arnd Bergmann wrote: > > From: Arnd Bergmann > > > > The ioread/iowrite functions on sh only do memory mapped I/O like the > > generic verion, and never map onto non-MMIO inb/outb varian

Re: [PATCH 00/13] lib/crc: improve how arch-optimized code is integrated

On Sun, Jun 01, 2025 at 03:44:28PM -0700, Eric Biggers wrote: > This series improves how lib/crc supports arch-optimized code. First, > instead of the arch-optimized CRC code being in arch/$(SRCARCH)/lib/, it > will now be in lib/crc/$(SRCARCH)/. Second, the API functions (e.g. > crc32c()), arch-

Re: [PATCH v2 00/12] lib/crc: improve how arch-optimized code is integrated

On Sat, Jun 07, 2025 at 05:47:02PM -0600, Jason A. Donenfeld wrote: > On Sat, Jun 07, 2025 at 01:04:42PM -0700, Eric Biggers wrote: > > Having arch-specific code outside arch/ was somewhat controversial when > > Zinc proposed it back in 2018. But I don't think the concerns are > > warranted. It's

Re: [PATCH] (powerpc/512) Fix possible `dma_unmap_single()` on uninitialized pointer

Thomas Fourier writes: > If the device configuration fails (if `dma_dev->device_config()`), > `sg_dma_address(&sg)` is not initialized and the jump to `err_dma_prep` > leads to calling `dma_unmap_single()` on `sg_dma_address(&sg)`. > > Signed-off-by: Thomas Fourier > --- > arch/powerpc/platforms

Re: [PATCH] powerpc: unify two CONFIG_POWERPC64_CPU entries in the same choice block

Masahiro Yamada writes: > There are two CONFIG_POWERPC64_CPU entries in the "CPU selection" > choice block. > > I guess the intent is to display a different prompt depending on > CPU_LITTLE_ENDIAN: "Generic (POWER5 and PowerPC 970 and above)" for big > endian, and "Generic (POWER8 and above)" for

Re: [PATCH] powerpc: use always-y instead of extra-y in Makefiles

Masahiro Yamada writes: > On Tue, Jun 3, 2025 at 3:50 PM Christophe Leroy > wrote: >> Le 02/06/2025 à 18:32, Masahiro Yamada a écrit : >> > The extra-y syntax is planned for deprecation because it is similar >> > to always-y. >> > >> > When building the boot wrapper, always-y and extra-y are equi

[mainline]Kernel OOPs at migrate_swap_task

Hello, IBM CI has reported a kernel oops, while running cpu monitor test [1], on the mainline kernel. [1]: https://github.com/avocado-framework-tests/avocado-misc-tests/blob/master/cpu/cpupower_monitor.py I am still in porcess of doing git bisect, meanwhile, wondering if below traces gi

Re: [PATCH] powerpc: use always-y instead of extra-y in Makefiles

On Mon, Jun 9, 2025 at 10:02 AM Michael Ellerman wrote: > > Masahiro Yamada writes: > > On Tue, Jun 3, 2025 at 3:50 PM Christophe Leroy > > wrote: > >> Le 02/06/2025 à 18:32, Masahiro Yamada a écrit : > >> > The extra-y syntax is planned for deprecation because it is similar > >> > to always-y.

Re: [PATCH] powerpc: unify two CONFIG_POWERPC64_CPU entries in the same choice block

On Mon, Jun 9, 2025 at 9:59 AM Michael Ellerman wrote: > > Masahiro Yamada writes: > > There are two CONFIG_POWERPC64_CPU entries in the "CPU selection" > > choice block. > > > > I guess the intent is to display a different prompt depending on > > CPU_LITTLE_ENDIAN: "Generic (POWER5 and PowerPC 9