From: Boqun Feng <boqun@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Carlos Llamas" <cmllamas@google.com>,
"Gary Guo" <gary@garyguo.net>, "Onur Özkan" <work@onurozkan.dev>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Benno Lossin" <lossin@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>, "Lyude Paul" <lyude@redhat.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Waiman Long" <longman@redhat.com>,
"Will Deacon" <will@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Alvin Sun" <alvin.sun@linux.dev>
Subject: Re: [PATCH v4 0/5] Rate limited printing for Rust
Date: Mon, 3 Aug 2026 19:18:35 -0700 [thread overview]
Message-ID: <anFL-74hn6QZjZGd@tardis.local> (raw)
In-Reply-To: <2026080337-careless-viper-7a1f@gregkh>
On Mon, Aug 03, 2026 at 08:24:16AM +0200, Greg Kroah-Hartman wrote:
> On Mon, Aug 03, 2026 at 06:56:50AM +0200, Miguel Ojeda wrote:
> > On Fri, Jul 31, 2026 at 2:20 PM Alice Ryhl <aliceryhl@google.com> 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?
Yeah.. I didn't find the time to pick these up, sorry about that.
> >
> > 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 a lot!
Regards,
Boqun
> thanks,
>
> greg k-h
prev parent reply other threads:[~2026-08-04 2:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 9:32 Alice Ryhl
2026-07-28 9:32 ` [PATCH v4 1/5] rust: sync: move lockdep types to rust/kernel/sync/lockdep.rs Alice Ryhl
2026-07-28 9:32 ` [PATCH v4 2/5] rust: sync: add const constructor for raw_spinlock_t Alice Ryhl
2026-07-28 9:32 ` [PATCH v4 3/5] rust: add pr_*_ratelimit! macros for printing Alice Ryhl
2026-07-28 9:32 ` [PATCH v4 4/5] rust_binder: consolidate transaction failure prints Alice Ryhl
2026-07-28 17:10 ` Carlos Llamas
2026-07-28 9:32 ` [PATCH v4 5/5] rust_binder: use pr_*_ratelimited! for printing Alice Ryhl
2026-07-31 9:06 ` [PATCH v4 0/5] Rate limited printing for Rust Greg Kroah-Hartman
2026-07-31 11:34 ` Miguel Ojeda
2026-07-31 12:19 ` Alice Ryhl
2026-08-03 4:56 ` Miguel Ojeda
2026-08-03 6:24 ` Greg Kroah-Hartman
2026-08-03 6:57 ` Miguel Ojeda
2026-08-11 12:36 ` Miguel Ojeda
2026-08-04 2:18 ` Boqun Feng [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=anFL-74hn6QZjZGd@tardis.local \
--to=boqun@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=alvin.sun@linux.dev \
--cc=bjorn3_gh@protonmail.com \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=will@kernel.org \
--cc=work@onurozkan.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®