Rust for Linux List
 help / color / mirror / Atom feed
From: "Rafael Passos" <rafael@rcpassos.me>
To: "kernel test robot" <lkp@intel.com>,
	"Rafael Passos" <rafael@rcpassos.me>,
	<rust-for-linux@vger.kernel.org>, <aliceryhl@google.com>,
	<gregkh@linuxfoundation.org>, <arve@android.com>,
	<tkjos@android.com>, "Christian Brauner" <brauner@kernel.org>,
	<cmllamas@google.com>
Cc: <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: Thu, 13 Aug 2026 10:15:46 -0300	[thread overview]
Message-ID: <DKNUE8CVHMBF.2I9WPCF66RLA7@rcpassos.me> (raw)
In-Reply-To: <202608102134.Dygd1Kx3-lkp@intel.com>

Hi Alice,

Do you want me to send a v3 with this rustfmt change ?

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-13 13:16 UTC|newest]

Thread overview: 4+ 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 [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=DKNUE8CVHMBF.2I9WPCF66RLA7@rcpassos.me \
    --to=rafael@rcpassos.me \
    --cc=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox