linux-kernel - Re: [PATCH v4 15/20] docs: add Rust documentation

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]

Date:   Thu, 17 Mar 2022 09:19:37 +0100
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Akira Yokosawa <akiyks@...il.com>
Cc:     Miguel Ojeda <ojeda@...nel.org>, Jonathan Corbet <corbet@....net>,
        Alex Gaynor <alex.gaynor@...il.com>,
        Adam Bratschi-Kaye <ark.email@...il.com>,
        Boris-Chengbiao Zhou <bobo1239@....de>,
        Wu XiangCheng <bobwxc@...il.cn>, Daniel Xu <dxu@...uu.xyz>,
        Gary Guo <gary@...yguo.net>,
        Greg KH <gregkh@...uxfoundation.org>,
        Yuki Okushi <jtitor@...6.org>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Finn Behrens <me@...enk.de>,
        Michal Marek <michal.lkml@...kovi.net>,
        Michael Ellerman <mpe@...erman.id.au>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        rust-for-linux <rust-for-linux@...r.kernel.org>,
        Sven Van Asbroeck <thesven73@...il.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Wedson Almeida Filho <wedsonaf@...gle.com>,
        Wei Liu <wei.liu@...nel.org>
Subject: Re: [PATCH v4 15/20] docs: add Rust documentation

Hi Akira,

On Mon, Feb 14, 2022 at 11:47 AM Akira Yokosawa <akiyks@...il.com> wrote:
>
> > diff --git a/Documentation/rust/logo.svg b/Documentation/rust/logo.svg
> > new file mode 100644
> > index 000000000000..65be792a5abe
> > --- /dev/null
>
> How about adding a suitable license identifier in a comment?

For the next round, I did not apply this suggestion, because it is
unclear which license identifier to use: it would be probably be the
same as the `COPYING-logo` one (which would be used also for the Tux
SVG, if it gets merged -- it was sent a while ago).

Cheers,
Miguel