[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250522094753.1369788-1-ojeda@kernel.org>
Date: Thu, 22 May 2025 11:47:53 +0200
From: Miguel Ojeda <ojeda@...nel.org>
To: richard120310@...il.com
Cc: a.hindborg@...nel.org,
alex.gaynor@...il.com,
aliceryhl@...gle.com,
benno.lossin@...ton.me,
bjorn3_gh@...tonmail.com,
boqun.feng@...il.com,
gary@...yguo.net,
jserv@...s.ncku.edu.tw,
linux-kernel-mentees@...ts.linux.dev,
linux-kernel@...r.kernel.org,
ojeda@...nel.org,
rust-for-linux@...r.kernel.org,
skhan@...uxfoundation.org,
tmgross@...ch.edu
Subject: Re: [PATCH] rust: list: Use "List::is_empty()" to perform checking when possible
On Mon, 10 Mar 2025 15:38:52 +0800 I Hsin Cheng <richard120310@...il.com> wrote:
>
> "List::is_empty()" provides a straight forward convention to check
> whether a given "List" is empty or not. There're numerous places in the
> current implementation still use "self.first.is_null()" to perform the
> equivalent check, replace them with "List::is_empty()".
>
> Signed-off-by: I Hsin Cheng <richard120310@...il.com>
Applied to `rust-next` -- thanks!
[ Rebased dropping the cases that do not apply anymore. - Miguel ]
Cheers,
Miguel
Powered by blists - more mailing lists