rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benno Lossin <benno.lossin@proton.me>
To: Aliet Exposito Garcia <aliet.exposito@gmail.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Alex Gaynor <alex.gaynor@gmail.com>,
	Wedson Almeida Filho <wedsonaf@gmail.com>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Andreas Hindborg" <a.hindborg@samsung.com>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 2/2] rust: Move `ARef<T>` and `AlwaysRefCounted` to new `sync::aref` module
Date: Thu, 19 Sep 2024 14:39:46 +0000	[thread overview]
Message-ID: <cc9cf121-93dc-43f7-97ef-e3532aae56d4@proton.me> (raw)
In-Reply-To: <20240918225115.2309224-3-aliet.exposito@gmail.com>

On 19.09.24 00:51, Aliet Exposito Garcia wrote:
> This patch refactors the `ARef` type and `AlwaysRefCounted` trait from
> `types.rs` into a new `sync/aref.rs` module.
> The type and trait definitions remain unchanged.
>  - Adds `rust/kernel/sync/aref.rs` with the definitions of `ARef` and
>     `AlwaysRefCounted`
>  - Removes the same type and trait definitions from `rust/kernel/types.rs`
>  - Updates relevant files to import `ARef` and `AlwaysRefCounted` from
>     `sync/aref.rs`
> 
> Suggested-by: Benno Lossin <benno.lossin@proton.me>
> 
> Link: https://github.com/Rust-for-Linux/linux/issues/1117
> Signed-off-by: Aliet Exposito Garcia <aliet.exposito@gmail.com>
> ---
>  drivers/block/rnull.rs             |   3 +-
>  rust/kernel/block/mq.rs            |   6 +-
>  rust/kernel/block/mq/operations.rs |   2 +-
>  rust/kernel/block/mq/request.rs    |   3 +-
>  rust/kernel/device.rs              |   8 +-
>  rust/kernel/sync.rs                |   1 +
>  rust/kernel/sync/aref.rs           | 152 +++++++++++++++++++++++++++++
>  rust/kernel/task.rs                |   4 +-
>  rust/kernel/types.rs               | 152 +----------------------------
>  9 files changed, 167 insertions(+), 164 deletions(-)
>  create mode 100644 rust/kernel/sync/aref.rs

Reviewed-by: Benno Lossin <benno.lossin@proton.me>

---
Cheers,
Benno


  reply	other threads:[~2024-09-19 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 22:51 [PATCH 0/2] rust: Move unfit code out of `rust/kernel/types.rs` Aliet Exposito Garcia
2024-09-18 22:51 ` [PATCH 1/2] rust: Move `FromBytes` and `AsBytes` traits to a new `transmute` module Aliet Exposito Garcia
2024-09-19 14:39   ` Benno Lossin
2024-09-20  9:20   ` Fiona Behrens
2024-09-18 22:51 ` [PATCH 2/2] rust: Move `ARef<T>` and `AlwaysRefCounted` to new `sync::aref` module Aliet Exposito Garcia
2024-09-19 14:39   ` Benno Lossin [this message]
2024-09-20  9:21   ` Fiona Behrens
2024-10-05 19:48 ` [PATCH 0/2] rust: Move unfit code out of `rust/kernel/types.rs` Miguel Ojeda
2024-10-06 19:29   ` Aliet Expósito
2024-10-07 17:11     ` Miguel Ojeda
2024-10-14 12:13   ` Miguel Ojeda

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=cc9cf121-93dc-43f7-97ef-e3532aae56d4@proton.me \
    --to=benno.lossin@proton.me \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=aliet.exposito@gmail.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=wedsonaf@gmail.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;
as well as URLs for NNTP newsgroup(s).