On Thu, May 28, 2026 at 12:44:15PM -0700, Ian Rogers wrote: > On Thu, May 28, 2026 at 12:32 PM Yury Norov <[email protected]> wrote: > > > > On Thu, May 28, 2026 at 12:29:03PM -0700, Andrew Morton wrote: > > > On Thu, 28 May 2026 15:26:28 -0400 Yury Norov <[email protected]> wrote: > > > > > > > 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? > > > > > > 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. > > > > > Roman, is there a list of trees/branches which Sashiko tries to apply > > > series to? > > > > Hi Roman, > > > > Can you add bitmap-for-next in the list? > > Fwiw, you can see the list of branches attempted and the SHA they are > at in the Baseline drop down: > > Baseline Status Log > tip/x86/core (0f61b1860cc3f52aef9036d7235ed1f017632193) Failed View Log > powerpc/HEAD (6916d5703ddf9a38f1f6c2cc793381a24ee914c6) Failed View Log > chanwoo/HEAD (7fd2df204f342fc17d1a0bfcd474b24232fb0f32) Failed View Log > linux-arm/HEAD (dd6c438c3e64a5ff0b5d7e78f7f9be547803ef1b) Failed View Log > linux-pm/HEAD (e7ae89a0c97ce2b68b0983cd01eda67cf373517d) Failed View Log > linux-fpga/HEAD Failed View Log > pci/HEAD (254f49634ee16a731174d2ae34bc50bd5f45e731) Failed View Log > linux-pm/thermal (21c315342b81526874acfa311f11b3f72bed4e14) Failed View Log > rdma/HEAD (67464f388d52ec172be62c99fc43697437ffa384) Failed View Log > linux-next/HEAD (f7af91adc230aa99e23330ecf85bc9badd9780ad) Failed View Log > HEAD (917719c412c48687d4a176965d1fa35320ec457c) Failed View Log
Thanks, Ian. Bitmap-for-next is tracked with linux-next.
