messages from 2023-03-20 00:57:12 to 2023-04-04 23:22:27 UTC [more...]
stack smashing detected
2023-04-04 23:22 UTC (17+ messages)
` core dump analysis, was "
[RFC PATCH v3] nubus: Don't list slot resources by default
2023-04-04 21:16 UTC (4+ messages)
[linux-next:master] BUILD REGRESSION 6a53bda3aaf3de5edeea27d0b1d8781d067640b6
2023-04-04 20:47 UTC
W sprawie samochodu
2023-04-04 7:50 UTC
[PATCH v3 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER
2023-04-04 11:50 UTC (21+ messages)
` [PATCH v3 01/14] arm: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER
` [PATCH v3 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v3 04/14] csky: drop ARCH_FORCE_MAX_ORDER
` [PATCH v3 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER
` [PATCH v3 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v3 07/14] nios2: "
` [PATCH v3 08/14] nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER
` [PATCH v3 09/14] powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v3 10/14] powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER
` [PATCH v3 11/14] sh: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v3 12/14] sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER
` [PATCH v3 13/14] sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v3 14/14] xtensa: "
[PATCH v1] m68k/mm: Use correct bit number in _PAGE_SWP_EXCLUSIVE comment
2023-04-04 8:56 UTC
[PATCH 00/21] dma-mapping: unify support for cache flushes
2023-04-04 8:27 UTC (61+ messages)
` [PATCH 01/21] openrisc: dma-mapping: flush bidirectional mappings
` [PATCH 02/21] xtensa: dma-mapping: use normal cache invalidation rules
` [PATCH 03/21] sparc32: flush caches in dma_sync_*for_device
` [PATCH 04/21] microblaze: dma-mapping: skip extra DMA flushes
` [PATCH 05/21] powerpc: dma-mapping: split out cache operation logic
` [PATCH 06/21] powerpc: dma-mapping: minimize for_cpu flushing
` [PATCH 07/21] powerpc: dma-mapping: always clean cache in _for_device() op
` [PATCH 08/21] riscv: dma-mapping: only invalidate after DMA, not flush
` [PATCH 09/21] riscv: dma-mapping: skip invalidation before bidirectional DMA
` [PATCH 10/21] csky: dma-mapping: skip invalidating before DMA from device
` [PATCH 11/21] mips: dma-mapping: skip invalidating before bidirectional DMA
` [PATCH 12/21] mips: dma-mapping: split out cache operation logic
` [PATCH 13/21] arc: dma-mapping: skip invalidating before bidirectional DMA
` [PATCH 14/21] parisc: dma-mapping: use regular flush/invalidate ops
` [PATCH 15/21] ARM: dma-mapping: always invalidate WT caches before DMA
` [PATCH 16/21] ARM: dma-mapping: bring back dmac_{clean,inv}_range
` [PATCH 17/21] ARM: dma-mapping: use arch_sync_dma_for_{device,cpu}() internally
` [PATCH 18/21] ARM: drop SMP support for ARM11MPCore
` [PATCH 19/21] ARM: dma-mapping: use generic form of arch_sync_dma_* helpers
` [PATCH 20/21] ARM: dma-mapping: split out arch_dma_mark_clean() helper
` [PATCH 21/21] dma-mapping: replace custom code with generic implementation
[geert-m68k:for-next] BUILD SUCCESS 1ea3bb3e4b767d074c8215c515e959c6420908bf
2023-04-04 7:18 UTC
[geert-m68k:master] BUILD SUCCESS 98485defdf60678296754fce632b05c68f447029
2023-04-03 21:53 UTC
Słowa kluczowe do wypozycjonowania
2023-03-29 7:29 UTC
[geert-m68k:master] BUILD SUCCESS 97e3e4fbb21e8f1f46dc0d13e72bd6b588626645
2023-03-27 23:06 UTC
[gerg-m68knommu:armnommu 3/3] arch/arm/include/asm/glue-cache.h:126:2: error: Unknown cache maintenance model
2023-03-27 22:08 UTC
gdb failure: "core file format not supported"
2023-03-27 8:34 UTC (4+ messages)
[PATCH v2] nubus: Don't list card resources by default
2023-03-26 8:23 UTC (14+ messages)
[PATCH v2 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER
2023-03-24 16:48 UTC (19+ messages)
` [PATCH v2 01/14] arm: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v2 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER
` [PATCH v2 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v2 04/14] csky: drop ARCH_FORCE_MAX_ORDER
` [PATCH v2 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER
` [PATCH v2 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v2 07/14] nios2: "
` [PATCH v2 08/14] nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER
` [PATCH v2 09/14] powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v2 10/14] powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER
` [PATCH v2 11/14] sh: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v2 12/14] sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER
` [PATCH v2 13/14] sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH v2 14/14] xtensa: "
[PATCH 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER
2023-03-23 17:11 UTC (24+ messages)
` [PATCH 01/14] arm: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER
` [PATCH 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH 04/14] csky: drop ARCH_FORCE_MAX_ORDER
` [PATCH 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER
` [PATCH 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH 07/14] nios2: "
` [PATCH 08/14] nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER
` [PATCH 09/14] powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH 10/14] powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER
` [PATCH 11/14] sh: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH 12/14] sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER
` [PATCH 13/14] sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text
` [PATCH 14/14] xtensa: "
[PATCH v4] Kconfig: introduce HAS_IOPORT option and select it as necessary
2023-03-23 16:33 UTC
[PATCH] m68k: Pass a pointer to virt_to_pfn() virt_to_page()
2023-03-23 15:09 UTC (3+ messages)
[PATCH v3 01/38] Kconfig: introduce HAS_IOPORT option and select it as necessary
2023-03-23 13:23 UTC (3+ messages)
[PATCH] nvme-tcp: fix nvme_tcp_term_pdu to match spec
2023-03-22 8:20 UTC (3+ messages)
[PATCH] nubus: Avoid scanning "private" card resources
2023-03-22 6:52 UTC (2+ messages)
REGARDS TO YOU
2023-03-22 0:23 UTC
[PATCH] nubus: Remove proc entries before adding them
2023-03-22 0:54 UTC
[geert-m68k:for-next] BUILD SUCCESS fda1941b8eab786112afe91088fa0a1ed4880360
2023-03-21 2:57 UTC
[geert-m68k:master] BUILD SUCCESS b55f773e598a93232307dc61278cdf081adad7fa
2023-03-21 2:57 UTC
[PATCH] m68k: Kconfig.machine: remove obsolete configs ROMBASE and ROMSIZE
2023-03-21 0:09 UTC (3+ messages)
[PATCH] nvme-tcp: Fix implicit padding in struct nvme_tcp_term_pdu
2023-03-20 15:39 UTC (3+ messages)
[PATCH] m68k: remove obsolete config NO_KERNEL_MSG
2023-03-20 14:31 UTC (2+ messages)
[PATCH v1] nubus: Remove redunant driver match function
2023-03-20 9:40 UTC (6+ messages)
` "
[PATCH AUTOSEL 5.4 04/12] m68k: Only force 030 bus error if PC not in exception table
2023-03-20 0:56 UTC
[PATCH AUTOSEL 4.19 4/9] m68k: Only force 030 bus error if PC not in exception table
2023-03-20 0:57 UTC
[PATCH AUTOSEL 4.14 4/9] m68k: Only force 030 bus error if PC not in exception table
2023-03-20 0:57 UTC
[PATCH AUTOSEL 5.15 06/17] m68k: Only force 030 bus error if PC not in exception table
2023-03-20 0:55 UTC
[PATCH AUTOSEL 5.10 05/15] m68k: Only force 030 bus error if PC not in exception table
2023-03-20 0:55 UTC
[PATCH AUTOSEL 6.1 06/29] m68k: mm: Fix systems with memory at end of 32-bit address space
2023-03-20 0:53 UTC (2+ messages)
` [PATCH AUTOSEL 6.1 07/29] m68k: Only force 030 bus error if PC not in exception table
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox