All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
	"Robin Murphy" <robin.murphy@arm.com>,
	iommu@lists.linux.dev, "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>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	rust-for-linux@vger.kernel.org, "Mark Brown" <broonie@kernel.org>
Subject: Re: [PATCH 1/2] rust: iommu: fix Rust formatting
Date: Thu, 22 Jan 2026 08:22:26 +0000	[thread overview]
Message-ID: <aXHeQi4xKRJGSHv6@google.com> (raw)
In-Reply-To: <20260121184339.74256-1-ojeda@kernel.org>

On Wed, Jan 21, 2026 at 07:43:38PM +0100, Miguel Ojeda wrote:
> The Rust kernel code should be kept `rustfmt`-clean [1].
> 
> Thus run the `rustfmt` target to fix the formatting issue.
> 
> Link: https://rust-for-linux.com/contributing#submit-checklist-addendum [1]
> Fixes: 2e2f6b0ef855 ("rust: iommu: add io_pgtable abstraction")
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

Thanks Miguel. For both patches:
Acked-by: Alice Ryhl <aliceryhl@google.com>

Alice

      parent reply	other threads:[~2026-01-22  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 18:43 [PATCH 1/2] rust: iommu: fix Rust formatting Miguel Ojeda
2026-01-21 18:43 ` [PATCH 2/2] rust: iommu: fix `srctree` link warning Miguel Ojeda
2026-01-22  8:19 ` [PATCH 1/2] rust: iommu: fix Rust formatting Joerg Roedel
2026-01-22  8:22 ` Alice Ryhl [this message]

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=aXHeQi4xKRJGSHv6@google.com \
    --to=aliceryhl@google.com \
    --cc=a.hindborg@kernel.org \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=broonie@kernel.org \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.