linux-kernel - Re: [PATCH v6 07/23] rust: import upstream `alloc` crate

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72nhKFFVHA9ZAfWw7=RTTcp_TUsgh8ENGsF8Gn_Qi=D2CQ@mail.gmail.com>
Date:   Sat, 7 May 2022 21:34:42 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Miguel Ojeda <ojeda@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        rust-for-linux <rust-for-linux@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jarkko Sakkinen <jarkko@...nel.org>,
        Alex Gaynor <alex.gaynor@...il.com>,
        Wedson Almeida Filho <wedsonaf@...gle.com>
Subject: Re: [PATCH v6 07/23] rust: import upstream `alloc` crate

On Sat, May 7, 2022 at 7:30 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> So I agree whole-heartedly with the "import the original, do the
> required changes separately", but I would like to see that original
> import really explicitly clarify the license status, and not require
> people to dig for it through external links.

Yeah, I should have noted the license in the message since now, with
the split patch, we do not even have the SPDX identifiers.

I can also add an explicit mention to the `README.md` file in the next
patch too.

Thanks for taking a look!

Cheers,
Miguel