From: "Onur Özkan" <work@onurozkan.dev>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rust-for-linux@vger.kernel.org, vireshk@kernel.org, nm@ti.com,
sboyd@kernel.org, ojeda@kernel.org, alex.gaynor@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
lossin@kernel.org, a.hindborg@kernel.org, aliceryhl@google.com,
tmgross@umich.edu, dakr@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: opp: use to_result for error handling
Date: Fri, 22 Aug 2025 08:13:43 +0300 [thread overview]
Message-ID: <20250822081343.4041a3d5@nimda.home> (raw)
In-Reply-To: <20250821092137.wttiixhiidt27hnq@vireshk-i7>
On Thu, 21 Aug 2025 14:51:37 +0530
Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 21-08-25, 12:16, Onur Özkan wrote:
> > Simplifies error handling by replacing the manual check
> > of the return value with the `to_result` helper.
> >
> > Signed-off-by: Onur Özkan <work@onurozkan.dev>
> > ---
> > rust/kernel/opp.rs | 16 +++++-----------
> > 1 file changed, 5 insertions(+), 11 deletions(-)
> >
> > diff --git a/rust/kernel/opp.rs b/rust/kernel/opp.rs
> > index 08126035d2c6..9d79c2816af5 100644
> > --- a/rust/kernel/opp.rs
> > +++ b/rust/kernel/opp.rs
> > @@ -12,7 +12,7 @@
> > clk::Hertz,
> > cpumask::{Cpumask, CpumaskVar},
> > device::Device,
> > - error::{code::*, from_err_ptr, from_result, to_result, Error,
> > Result, VTABLE_DEFAULT_ERROR},
> > + error::{code::*, from_err_ptr, from_result, to_result, Result,
> > VTABLE_DEFAULT_ERROR}, ffi::c_ulong,
> > prelude::*,
> > str::CString,
> > @@ -500,11 +500,8 @@ pub fn set(self, dev: &Device) ->
> > Result<ConfigToken> { // requirements. The OPP core guarantees not
> > to access fields of [`Config`] after this call // and so we don't
> > need to save a copy of them for future use. let ret = unsafe {
> > bindings::dev_pm_opp_set_config(dev.as_raw(), &mut config) };
> > - if ret < 0 {
> > - Err(Error::from_errno(ret))
> > - } else {
> > - Ok(ConfigToken(ret))
> > - }
> > +
> > + to_result(ret).map(|()| ConfigToken(ret))
> > }
> >
> > /// Config's clk callback.
> > @@ -713,11 +710,8 @@ pub fn opp_count(&self) -> Result<u32> {
> > // SAFETY: The requirements are satisfied by the existence
> > of [`Device`] and its safety // requirements.
> > let ret = unsafe {
> > bindings::dev_pm_opp_get_opp_count(self.dev.as_raw()) };
> > - if ret < 0 {
> > - Err(Error::from_errno(ret))
> > - } else {
> > - Ok(ret as u32)
> > - }
> > +
> > + to_result(ret).map(|()| ret as u32)
> > }
>
> I would get rid of `ret` as well in both the cases, like it is done by
> other users of `to_result()`.
>
`ret` is returned at the end unlike other `to_result` usages in other
functions.
-Onur
next prev parent reply other threads:[~2025-08-22 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 9:16 [PATCH] rust: opp: use to_result for error handling Onur Özkan
2025-08-21 9:21 ` Viresh Kumar
2025-08-22 5:13 ` Onur Özkan [this message]
2025-08-22 5:52 ` Viresh Kumar
2025-08-22 5:53 ` Viresh Kumar
2025-08-25 22:56 ` Elle Rhumsaa
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=20250822081343.4041a3d5@nimda.home \
--to=work@onurozkan.dev \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nm@ti.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).