From: Carlos Llamas <cmllamas@google.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Boqun Feng" <boqun@kernel.org>, "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
Subject: Re: [PATCH v4 4/5] rust_binder: consolidate transaction failure prints
Date: Tue, 28 Jul 2026 17:10:31 +0000 [thread overview]
Message-ID: <amjih6MHfDIAk0QA@google.com> (raw)
In-Reply-To: <20260728-pr-ratelimited-v4-4-435f8d6e9605@google.com>
On Tue, Jul 28, 2026 at 09:32:54AM +0000, Alice Ryhl wrote:
> When a transaction fails, it currently hits multiple print statements
> meaning that a single failure can result in several lines in the kernel
> log. This is unnecessary, so consolidate them into one print used for
> all transaction failures.
>
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
> ---
Thanks,
Acked-by: Carlos Llamas <cmllamas@google.com>
next prev parent reply other threads:[~2026-07-28 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 9:32 [PATCH v4 0/5] Rate limited printing for Rust 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 [this message]
2026-07-28 9:32 ` [PATCH v4 5/5] rust_binder: use pr_*_ratelimited! for printing Alice Ryhl
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=amjih6MHfDIAk0QA@google.com \
--to=cmllamas@google.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--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=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