[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <622e155f-2ad0-4f62-a6a7-c9c88903db82@kernel.dk>
Date: Thu, 15 Aug 2024 10:00:53 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Andreas Hindborg <nmi@...aspace.dk>,
Andreas Hindborg <a.hindborg@...sung.com>, Boqun Feng
<boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Alice Ryhl <aliceryhl@...gle.com>,
"Behme Dirk (XC-CP/ESB5)" <Dirk.Behme@...bosch.com>,
linux-block@...r.kernel.org, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] rust: fix erranous use of lock class key in rust
block device bindings
On 8/15/24 9:31 AM, Miguel Ojeda wrote:
> Hi Jens,
>
> On Thu, Aug 15, 2024 at 4:22?PM Jens Axboe <axboe@...nel.dk> wrote:
>>
>> Applied, thanks!
>>
>> [2/2] rust: block: fix wrong usage of lockdep API
>> commit: d28b514ea3ae15274a4d70422ecc873bf6258e77
>
> If you picked 2/2 only, it requires the former as far as I understand.
Sorry I missed that, mostly because they were split into two separate
postings. Hence it only pulled one.
> If you want to pick both:
>
> Acked-by: Miguel Ojeda <ojeda@...nel.org>
>
> Otherwise, I am happy to take them too.
Go ahead and take them, I'll just kill the one I have. Thanks!
--
Jens Axboe
Powered by blists - more mailing lists