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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <7C1E7AC4-67A0-4CD5-8B22-490F53BDBF1E@collabora.com>
Date: Sat, 19 Jul 2025 21:34:29 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Miguel Ojeda <ojeda@...nel.org>,
 Alex Gaynor <alex.gaynor@...il.com>,
 Boqun Feng <boqun.feng@...il.com>,
 Gary Guo <gary@...yguo.net>,
 Björn Roy Baron <bjorn3_gh@...tonmail.com>,
 Benno Lossin <lossin@...nel.org>,
 Andreas Hindborg <a.hindborg@...nel.org>,
 Alice Ryhl <aliceryhl@...gle.com>,
 Trevor Gross <tmgross@...ch.edu>,
 Danilo Krummrich <dakr@...nel.org>,
 "Rafael J. Wysocki" <rafael@...nel.org>,
 linux-kernel@...r.kernel.org,
 rust-for-linux@...r.kernel.org,
 Fiona Behrens <me@...enk.dev>
Subject: Re: [PATCH v15 0/3] rust: platform: add Io support

Hi Greg,

> On 19 Jul 2025, at 05:01, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> 
> On Thu, Jul 17, 2025 at 12:55:21PM -0300, Daniel Almeida wrote:
>> ---
>> Daniel Almeida (3):
>>      rust: io: add resource abstraction
>>      rust: io: mem: add a generic iomem abstraction
>>      rust: platform: add resource accessors
>> 
>> rust/bindings/bindings_helper.h |   1 +
>> rust/helpers/io.c               |  41 ++++++
>> rust/kernel/io.rs               |   5 +
>> rust/kernel/io/mem.rs           | 283 ++++++++++++++++++++++++++++++++++++++++
>> rust/kernel/io/resource.rs      | 229 ++++++++++++++++++++++++++++++++
>> rust/kernel/platform.rs         |  60 ++++++++-
>> 6 files changed, 618 insertions(+), 1 deletion(-)
> 
> Who is going to be responsible for the new files you have added?

As Danilo said, there will be a separate entry for the Rust I/O code, which
I’ve agreed to share the responsibility for.

> 
> And no real objection, but no copyright info was added to them either,
> was that intentional?  I know some companies frown on that as it goes
> against their corporate policy (but some don't care, it's hard to keep
> track of who likes what at times...)
> 
> thanks,
> 
> greg k-h
> 

Good catch. It wasn't intentional, but I don't think it will be a problem.

-- Daniel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ