Re: [PATCH v4 0/5] Rate limited printing for Rust
Greg Kroah-Hartman <[email protected]> Mon, 3 Aug 2026 08:24:16 +0200
| Newsgroups | org.kernel.vger.rust-for-linux,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <2026080337-careless-viper-7a1f@gregkh> |
On Mon, Aug 03, 2026 at 06:56:50AM +0200, Miguel Ojeda wrote: > On Fri, Jul 31, 2026 at 2:20 PM Alice Ryhl <[email protected]> wrote: > > > > It's not too long until the next cycle so going via Rust tree is ok with me. > > > > I'd appreciate if at least the first three could go together so we > > don't have split it over three release cycles, though. > > Ok, Boqun: I think you didn't pick the first two for your tip PR, > shall I or Greg do it then? > > Greg: should I pick all this through Rust, i.e. including Binder's, or > leave the Binder ones out, or do you want to pick them all? I'd love to just take them all at once if no one objects, as odds are there are going to be binder merge conflicts due to the printk() changes in that codebase in the char-misc-next tree. thanks, greg k-h