Rust for Linux List
 help / color / mirror / Atom feed
From: Alvin Sun <alvin.sun@linux.dev>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Andreas Hindborg" <a.hindborg@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Tamir Duberstein" <tamird@kernel.org>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Onur Özkan" <work@onurozkan.dev>,
	linux-block@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] rust: block: gen_disk: set fops.owner from driver module pointer
Date: Tue, 11 Aug 2026 21:53:54 +0800	[thread overview]
Message-ID: <15a4a6c2-1806-45ec-8293-b868a584bd25@linux.dev> (raw)
In-Reply-To: <CANiq72nmthEu5HQG9B2yOgLvhEJ+PMO7OBG-ki2uUQiUTTgciw@mail.gmail.com>


On 8/11/26 20:20, Miguel Ojeda wrote:
> On Tue, Aug 11, 2026 at 8:51 AM Alvin Sun <alvin.sun@linux.dev> wrote:
>> This patch was meant to be sent separately, but I forgot to send it.
> Do you mean "not separately"? i.e. in the series?

Hi Miguel,

Thanks for taking a look.

To clarify: when I sent the fops.owner series, I did indeed overlook
`GenDisk`. After the series was out, I realized the gap, prepared this
patch, and privately asked Andreas (back in late June) for his
thoughts. He suggested sending it standalone with the series as a
dependency. I then got sidetracked by other things and forgot to send
it out.

Best regards,
Alvin

>
> I asked Andreas for his Acked-by.
>
> Cheers,
> Miguel

      reply	other threads:[~2026-08-11 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  6:51 [PATCH] rust: block: gen_disk: set fops.owner from driver module pointer Alvin Sun
2026-08-11 12:20 ` Miguel Ojeda
2026-08-11 13:53   ` Alvin Sun [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=15a4a6c2-1806-45ec-8293-b868a584bd25@linux.dev \
    --to=alvin.sun@linux.dev \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=linux-block@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=work@onurozkan.dev \
    /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