All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.com>
To: Rafael Passos <rafael@rcpassos.me>
Cc: kernel test robot <lkp@intel.com>,
	rust-for-linux@vger.kernel.org,  gregkh@linuxfoundation.org,
	arve@android.com, tkjos@android.com,
	 Christian Brauner <brauner@kernel.org>,
	cmllamas@google.com, oe-kbuild-all@lists.linux.dev,
	 Shuah Khan <skhan@linuxfoundation.org>,
	Brigham Campbell <me@brighamcampbell.com>,
	 Jori Koolstra <jkoolstra@xs4all.nl>
Subject: Re: [PATCH v2] rust_binder: speed up get_node_debug_info using lower_bound iter
Date: Fri, 14 Aug 2026 20:58:42 +0000	[thread overview]
Message-ID: <an-Bgkfg6LcbQDGs@google.com> (raw)
In-Reply-To: <DKNUE8CVHMBF.2I9WPCF66RLA7@rcpassos.me>

On Thu, Aug 13, 2026 at 10:15:46AM -0300, Rafael Passos wrote:
> Hi Alice,
> 
> Do you want me to send a v3 with this rustfmt change ?

Yes please make sure your patch passes rustfmt.

Thanks, Alice

> On Mon Aug 10, 2026 at 4:29 PM -03, kernel test robot wrote:
> > ...
> >             {
> >                 let inner = self.inner.lock();
> >                 // cursor_lower_bound retrieves the "key" passed or the next existing larger key
> >    -            if let Some(cursor) = inner.nodes.cursor_lower_bound(&(ptr+1)){
> >    +            if let Some(cursor) = inner.nodes.cursor_lower_bound(&(ptr + 1)) {
> >                     let (_, node) = cursor.current();
> 
> Thanks,
> Rafael Passos

      reply	other threads:[~2026-08-14 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 13:31 [PATCH v2] rust_binder: speed up get_node_debug_info using lower_bound iter Rafael Passos
2026-08-04 13:14 ` Alice Ryhl
2026-08-10 19:29 ` kernel test robot
2026-08-13 13:15   ` Rafael Passos
2026-08-14 20:58     ` Alice Ryhl [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=an-Bgkfg6LcbQDGs@google.com \
    --to=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=cmllamas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkoolstra@xs4all.nl \
    --cc=lkp@intel.com \
    --cc=me@brighamcampbell.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rafael@rcpassos.me \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tkjos@android.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.