From: "Onur Özkan" <work@onurozkan.dev>
To: rust-for-linux@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, daniel@sedlak.dev,
dirk.behme@de.bosch.com, felipe_life@live.com, tamird@gmail.com,
dakr@kernel.org, tmgross@umich.edu, aliceryhl@google.com,
a.hindborg@kernel.org, lossin@kernel.org,
bjorn3_gh@protonmail.com, gary@garyguo.net, boqun.feng@gmail.com,
alex.gaynor@gmail.com, ojeda@kernel.org,
"Onur Özkan" <work@onurozkan.dev>
Subject: [PATCH v2 0/1] rust: refactor to_result to return the original value
Date: Tue, 9 Sep 2025 20:00:12 +0300 [thread overview]
Message-ID: <20250909170013.16025-1-work@onurozkan.dev> (raw)
Changelog in v2:
- Removed `map(|_| ())` calls from v1 and replaced them with
`to_result(...)?` and `Ok(())` (except miscdevice.rs, as it
required `Ok::<(), Error>(())` which is less clean).
- Rebased on latest regulator/for-next and fixed the build error.
Onur Özkan (1):
rust: refactor to_result to return the original value
rust/kernel/auxiliary.rs | 3 ++-
rust/kernel/block/mq/tag_set.rs | 3 ++-
rust/kernel/cpufreq.rs | 5 +++--
rust/kernel/devres.rs | 3 ++-
rust/kernel/dma.rs | 11 ++++++++---
rust/kernel/error.rs | 17 ++++++++++++-----
rust/kernel/miscdevice.rs | 2 +-
rust/kernel/mm/virt.rs | 3 ++-
rust/kernel/pci.rs | 6 ++++--
rust/kernel/platform.rs | 3 ++-
rust/kernel/regulator.rs | 14 ++++++++------
11 files changed, 46 insertions(+), 24 deletions(-)
--
2.50.0
next reply other threads:[~2025-09-09 17:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 17:00 Onur Özkan [this message]
2025-09-09 17:00 ` [PATCH v2 1/1] " Onur Özkan
2025-09-09 17:17 ` Miguel Ojeda
2025-09-09 17:43 ` Onur Özkan
2025-09-09 18:25 ` Onur
2025-09-09 18:25 ` Daniel Almeida
2025-09-09 18:53 ` Onur Özkan
2025-09-09 20:13 ` Daniel Almeida
2025-09-09 20:05 ` Miguel Ojeda
2025-09-09 20:12 ` Daniel Almeida
2025-09-09 20:25 ` Miguel Ojeda
2025-09-10 4:50 ` Onur Özkan
2025-09-10 6:26 ` Alice Ryhl
2025-09-10 10:58 ` Onur Özkan
2025-09-10 11:05 ` Alice Ryhl
2025-09-10 12:47 ` Onur Özkan
2025-09-10 12:50 ` Alice Ryhl
2025-09-10 12:55 ` Onur Özkan
2025-09-12 8:41 ` kernel test robot
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=20250909170013.16025-1-work@onurozkan.dev \
--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=daniel@sedlak.dev \
--cc=dirk.behme@de.bosch.com \
--cc=felipe_life@live.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
/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
all inboxes | Powered by JetHome®