linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Daniel Almeida" <daniel.almeida@collabora.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	"Fiona Behrens" <me@kloenk.dev>
Subject: Re: [PATCH v15 0/3] rust: platform: add Io support
Date: Sun, 20 Jul 2025 19:46:46 +0200	[thread overview]
Message-ID: <DBH2JSV0SKWO.3FE776WW2O2D5@kernel.org> (raw)
In-Reply-To: <20250717-topics-tyr-platform_iomem-v15-0-beca780b77e3@collabora.com>

On Thu Jul 17, 2025 at 5:55 PM CEST, Daniel Almeida wrote:
> Daniel Almeida (3):
>       rust: io: add resource abstraction

    [ Capitalize safety comments and end it with a period. - Danilo ]

>       rust: io: mem: add a generic iomem abstraction

    [ Add #[expect(dead_code)] to avoid a temporary warning, remove
      unnecessary OF_ID_TABLE constants in doc-tests and ignore doc-tests
      for now to avoid a temporary build failure. - Danilo ]

>       rust: platform: add resource accessors

    [ Remove #[expect(dead_code)] from IoRequest::new() and move SAFETY
      comments right on top of unsafe blocks to avoid clippy warnings for
      some (older) clippy versions. - Danilo ]

Applied to driver-core-testing, thanks!

  parent reply	other threads:[~2025-07-20 17:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17 15:55 [PATCH v15 0/3] rust: platform: add Io support Daniel Almeida
2025-07-17 15:55 ` [PATCH v15 1/3] rust: io: add resource abstraction Daniel Almeida
2025-07-17 15:55 ` [PATCH v15 2/3] rust: io: mem: add a generic iomem abstraction Daniel Almeida
2025-07-17 19:45   ` Danilo Krummrich
2025-07-18 12:23     ` Daniel Almeida
2025-07-19 13:51   ` Danilo Krummrich
2025-07-19 14:08     ` [PATCH] rust: io: mem: enable IoRequest doc-tests Danilo Krummrich
2025-07-20 17:47       ` Danilo Krummrich
2025-07-17 15:55 ` [PATCH v15 3/3] rust: platform: add resource accessors Daniel Almeida
2025-07-19 13:15   ` Danilo Krummrich
2025-07-19 16:19     ` Miguel Ojeda
2025-07-19 16:29       ` Miguel Ojeda
2025-07-19  8:01 ` [PATCH v15 0/3] rust: platform: add Io support Greg Kroah-Hartman
2025-07-19 10:16   ` Danilo Krummrich
2025-07-20  0:34   ` Daniel Almeida
2025-07-20 17:46 ` Danilo Krummrich [this message]
2025-07-23  7:35 ` Dirk Behme
2025-07-23 13:33   ` Daniel Almeida

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=DBH2JSV0SKWO.3FE776WW2O2D5@kernel.org \
    --to=dakr@kernel.org \
    --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=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=me@kloenk.dev \
    --cc=ojeda@kernel.org \
    --cc=rafael@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).