linux-kernel - Re: [PATCH v1 0/5] rust: Add ACPI match table support for Rust drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2d02be52-b22b-4a2b-bfbe-aff7b62200e8@yahoo.com>
Date: Thu, 5 Jun 2025 14:57:21 +0100
From: Igor Korotin <igor.korotin@...oo.com>
To: Danilo Krummrich <dakr@...nel.org>,
 Igor Korotin <igor.korotin.linux@...il.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
 Rob Herring <robh@...nel.org>, Saravana Kannan <saravanak@...gle.com>,
 "Rafael J . Wysocki" <rafael@...nel.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-acpi@...r.kernel.org, devicetree@...r.kernel.org,
 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>,
 Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>,
 Trevor Gross <tmgross@...ch.edu>, Len Brown <lenb@...nel.org>,
 Viresh Kumar <viresh.kumar@...aro.org>,
 Wedson Almeida Filho <wedsonaf@...il.com>, Alex Hung <alex.hung@....com>,
 Tamir Duberstein <tamird@...il.com>,
 FUJITA Tomonori <fujita.tomonori@...il.com>,
 Xiangfei Ding <dingxiangfei2009@...il.com>
Subject: Re: [PATCH v1 0/5] rust: Add ACPI match table support for Rust
 drivers

> Thanks this is great!
> 
> Unfortunately, it seems that something went wrong sending this patch series.
> Patches 3 and 5 are missing on my end (and on the corresponding lists as well).

Yes, I know. Gmail has blocked me from sending any letters. I probably hit
some limit. It will likely unblock me sometime today or tomorrow.

> Also, technically this series is a v2; patch 1 differs from the one you sent
> originally -- please include a changelog.

Because of this Gmail issue, I need to clarify the right course of 
action to avoid being blocked again:
Should I resend the whole series as PATCH v2 with a changelog?

Thanks
Igor