Re: [PATCH 00/16] lib/cpumask: get rid of cpumap_print_to_pagebuf()
Andrew Morton <[email protected]> Thu, 28 May 2026 13:02:11 -0700
| Newsgroups | org.kernel.vger.linux-fpga,dev.linux.lists.driver-core,dev.linux.lists.imx,dev.linux.lists.nvdimm,org.infradead.lists.linux-amlogic,org.infradead.lists.linux-rockchip,org.kernel.vger.linux-acpi,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-cxl,org.kernel.vger.linux-kernel,org.kernel.vger.linux-pci,org.kernel.vger.linux-perf-users,org.kernel.vger.linux-pm,org.kernel.vger.linux-rdma,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 28 May 2026 15:32:34 -0400 Yury Norov <[email protected]> wrote: > > > > Sashiko doesn't attempt bitmap-for-next, so it couldn't apply this series. > > > > https://sashiko.dev/#/patchset/[email protected] > > > > > > OK... What should I do about that? > > > > Rebase onto something which Sashiko *does* attempt. Mainline, a few > > mm.git branches. Maybe linux-next. > > Is Sashiko a new mandatory requirement now? Documentation doesn't even > mention the bot. It's early days and things are still evolving. No, I'm not aware of any team having made it mandatory but boy it's helpful. Authors appreciate it because it finds bugs, and nobody wants to add bugs to Linux.