Rust for Linux List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: jahnavimn@google.com, "Arve Hjønnevåg" <arve@android.com>,
	"Todd Kjos" <tkjos@android.com>,
	"Christian Brauner" <brauner@kernel.org>,
	"Carlos Llamas" <cmllamas@google.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Tamir Duberstein" <tamird@kernel.org>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Onur Özkan" <work@onurozkan.dev>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v3 0/7] rust_binder : Implement dynamic debug logging mask
Date: Thu, 16 Jul 2026 08:04:22 +0200	[thread overview]
Message-ID: <2026071634-democracy-elves-5686@gregkh> (raw)
In-Reply-To: <ald6JiykrvSDxzWj@google.com>

On Wed, Jul 15, 2026 at 12:16:38PM +0000, Alice Ryhl wrote:
> On Mon, Jul 13, 2026 at 12:35:22PM +0000, Jahnavi MN via B4 Relay wrote:
> > base-commit: f8d269390cd2a7a9fb5a31f153e7c7b709defea0
> 
> Greg, a quick practical question. This doesn't apply anymore because of
> the merge commit, and it actually also has a conflict with the fix
> "rust_binder: only print failure if error has source". (Both conflicts
> are in the same chunk of code.)
> 
> The rebase of this series that I'm currently using for my development is
> this one:
> https://github.com/Darksonn/linux/commits/rust-binder-base/
> 
> That rebase happens to fix the conflict with the merge commit in a way
> that implicitly fixes the same issue as "rust_binder: only print failure
> if error has source". So with that rebase, the fix patch is only
> relevant for 7.2 and the stable backports. (i.e. merge conflict fix is
> to keep char-misc-next side)
> 
> Do you want a resend of this that looks like that?

Yes please send a new series that I can actually apply.

> As for my other series, the netlink series [1] applies cleanly on
> char-misc-next both before and after applying the debug mask changes (or
> at least, they cherry-pick cleanly after 'git am'ing on the original
> base commit).

Are they ready to be applied?  If so, I'll pick them up.

> And the ratelimited printing [2] and synchronize_rcu() series [3] both
> need new versions with changes, but I'd like to base them on top of the
> debug mask and netlink patchsets.

No problems, just send those again too please.

thanks,

greg k-h

  reply	other threads:[~2026-07-16  6:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 12:35 [PATCH v3 0/7] rust_binder : Implement dynamic debug logging mask Jahnavi MN via B4 Relay
2026-07-13 12:35 ` [PATCH v3 1/7] rust_binder: Add " Jahnavi MN via B4 Relay
2026-07-13 12:35 ` [PATCH v3 2/7] rust_binder: Implement BINDER_DEBUG_USER_ERROR for freezer-related operation Jahnavi MN via B4 Relay
2026-07-13 12:35 ` [PATCH v3 3/7] rust_binder: Implement BINDER_DEBUG_USER_ERROR for refcounting and death notifications Jahnavi MN via B4 Relay
2026-07-13 12:35 ` [PATCH v3 4/7] rust_binder: Implement BINDER_DEBUG_USER_ERROR for transaction parsing failures Jahnavi MN via B4 Relay
2026-07-13 12:35 ` [PATCH v3 5/7] rust_binder: Implement BINDER_DEBUG_FAILED_TRANSACTION Jahnavi MN via B4 Relay
2026-07-13 12:35 ` [PATCH v3 6/7] rust_binder: Implement BINDER_DEBUG_DEATH_NOTIFICATION Jahnavi MN via B4 Relay
2026-07-13 12:35 ` [PATCH v3 7/7] rust_binder: Implement BINDER_DEBUG_DEAD_TRANSACTION Jahnavi MN via B4 Relay
2026-07-13 21:04   ` Carlos Llamas
2026-07-15 12:16 ` [PATCH v3 0/7] rust_binder : Implement dynamic debug logging mask Alice Ryhl
2026-07-16  6:04   ` Greg Kroah-Hartman [this message]
2026-07-16  6:45     ` 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=2026071634-democracy-elves-5686@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=brauner@kernel.org \
    --cc=cmllamas@google.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=jahnavimn@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tkjos@android.com \
    --cc=tmgross@umich.edu \
    --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