From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 3/4] docs/images: adding default buildroot linux logo
Date: Mon, 27 Aug 2018 11:05:35 +0200 [thread overview]
Message-ID: <20180827110535.431744f8@windsurf> (raw)
In-Reply-To: <1535118300-26815-3-git-send-email-angelo@amarulasolutions.com>
Hello,
On Fri, 24 Aug 2018 15:44:59 +0200, Angelo Compagnucci wrote:
> From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
>
> This patch adds a default buildroot linux boot up logo that can
> be used in all buildroot defconfigs as a buildroot watermark.
>
> Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
> ---
> docs/website/images/logo_linux_clut224.png | Bin 0 -> 6825 bytes
Is docs/website/images/ really the right place for this ? Shouldn't
this go in linux/ instead ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-27 9:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 13:44 [Buildroot] [PATCH v4 1/4] package/imagemagick: add host package Angelo Compagnucci
2018-08-24 13:44 ` [Buildroot] [PATCH v4 2/4] linux: add custom linux logo Angelo Compagnucci
2018-08-24 21:19 ` Yann E. MORIN
2018-10-21 16:15 ` Peter Korsgaard
2018-08-24 13:44 ` [Buildroot] [PATCH v4 3/4] docs/images: adding default buildroot " Angelo Compagnucci
2018-08-24 21:27 ` Yann E. MORIN
2018-08-27 9:05 ` Thomas Petazzoni [this message]
2018-08-27 9:07 ` Angelo Compagnucci
2018-08-24 13:45 ` [Buildroot] [PATCH v4 4/4] configs: add linux boot logo to a selection of configs Angelo Compagnucci
2018-08-24 21:49 ` Yann E. MORIN
2018-08-24 22:55 ` Angelo Compagnucci
2018-08-25 7:33 ` Yann E. MORIN
2018-08-27 9:08 ` Thomas Petazzoni
2018-08-27 17:34 ` Angelo Compagnucci
2018-08-24 21:17 ` [Buildroot] [PATCH v4 1/4] package/imagemagick: add host package Yann E. MORIN
2018-10-21 15:23 ` Peter Korsgaard
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=20180827110535.431744f8@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.