From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Garrett LeSage <garrett@lesage.us>,
IFo Hancroft <contact@ifohancroft.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] docs: add SVG version of the Linux logo
Date: Thu, 2 Jun 2022 09:39:46 +0200 [thread overview]
Message-ID: <CAMuHMdUa+JJ-mwTtveerndzmjVV95tqK1iWDRDPDRf6MPtpvww@mail.gmail.com> (raw)
In-Reply-To: <20220528153132.8636-2-ojeda@kernel.org>
Hi Miguel,
On Sat, May 28, 2022 at 10:15 PM Miguel Ojeda <ojeda@kernel.org> wrote:
> In the Rust for Linux patch series, Jonathan Corbet requested [1] that
> we avoid binary assets (such as the logo), possibly by recreating
> them in SVG format.
>
> However, it turns out there is no SVG version of the Linux logo
> in the kernel tree yet, only a GIF one from the pre-v2.0.0 days.
>
> This patch fixes that by adding a SVG version of the Linux logo,
> which we could then use in the Rust for Linux documentation and
> other similar places.
Perhaps you want to add a Rust logo to drivers/video/logo/, to be
shown using fb_append_extra_logo() when Rust technology is included?
;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2022-06-02 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 15:31 [PATCH v2 1/2] docs: move Linux logo into a new `images` folder Miguel Ojeda
2022-05-29 0:24 ` Bagas Sanjaya
2022-05-29 14:27 ` Jonathan Corbet
2022-06-01 15:33 ` Jonathan Corbet
[not found] ` <20220528153132.8636-2-ojeda@kernel.org>
2022-06-02 7:39 ` Geert Uytterhoeven [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMuHMdUa+JJ-mwTtveerndzmjVV95tqK1iWDRDPDRf6MPtpvww@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=contact@ifohancroft.com \
--cc=corbet@lwn.net \
--cc=garrett@lesage.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).