Re: [PATCH 00/16] lib/cpumask: get rid of cpumap_print_to_pagebuf()
Yury Norov <[email protected]> Thu, 28 May 2026 15:26:28 -0400
| 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 | <ahiW5LKLiPMC6il_@yury> |
On Thu, May 28, 2026 at 12:18:06PM -0700, Andrew Morton wrote: > On Thu, 28 May 2026 14:36:07 -0400 Yury Norov <[email protected]> wrote: > > > cpumap_print_to_pagebuf() is the equivalent for the "&*pb[l]" notation > > in printk-like functions. In some cases, it makes people to create > > temporary buffers for the printed cpumasks, where it can be avoided. > > > > Get rid of it in a favor of more standard printing API. > > > > Each patch, except for the last one, is independent and may be moved with > > the corresponding subsystem. Or I can take it in bitmap-for-next, at > > maintainers' discretion. > > > > On top of bitmap-for-next. > > 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?