From: Vincent Mailhol <mailhol@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Helge Deller <deller@gmx.de>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] video/logo: Improve logo help texts
Date: Wed, 23 Sep 2026 13:23:08 +0200 [thread overview]
Message-ID: <385341aa-db86-4f22-851f-85c0e6a0ca89@kernel.org> (raw)
In-Reply-To: <024a2d7e9a6b63d261f6ca4afb1a75d4f540defa.1790154481.git.geert+renesas@glider.be>
On 23/09/2026 at 11:09, Geert Uytterhoeven wrote:
> Since commit dfa6ce636cb8faea ("video/logo: allow custom logo"), the
> LOGO_LINUX_{MONO,VGA16,CLUT224} configuration options no longer control
> the inclusion of the "standard" Linux logo, but the inclusion of
> (possibly custom) logos specified through the correspondig *_FILE
^^^^^^^^^^^^
Typo: corresponding (missing 'n')
> options.
>
> Adjust the one-line prompt to reflect this.
> Add long help texts while at it.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
I added some comments, but notwithstanding of these:
Acked-by: Vincent Mailhol <mailhol@kernel.org>
> ---
> drivers/video/logo/Kconfig | 21 ++++++++++++++++++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/video/logo/Kconfig b/drivers/video/logo/Kconfig
> index cda15b95891ed3a8..3cb66ac88d6be0fe 100644
> --- a/drivers/video/logo/Kconfig
> +++ b/drivers/video/logo/Kconfig
> @@ -19,7 +19,11 @@ config FB_LOGO_EXTRA
> default y if SPU_BASE
>
> config LOGO_LINUX_MONO
> - bool "Standard black and white Linux logo"
> + bool "Black and white Linux logo"
> + help
> + Include a monochrome (black and white) Linux logo.
> + This logo can be shown on all kinds of displays.
> + Say Y to show a logo on monochrome displays.
>
> config LOGO_LINUX_MONO_FILE
> string "Monochrome logo .pbm file"
> @@ -36,7 +40,13 @@ config LOGO_LINUX_MONO_FILE
> magick source_image -compress none destination.pbm
>
> config LOGO_LINUX_VGA16
> - bool "Standard 16-color Linux logo"
> + bool "16-color Linux logo"
> + help
> + Include a 16-color Linux logo.
> + This logo can be shown on displays that support showing (at least)
> + the standard VGA 16 color palette.
> + Say Y to show a logo on color displays that are limited to less than
> + 256 colors.
Maybe state that if supported, this takes precedence on the monochrome logo.
> config LOGO_LINUX_VGA16_FILE
> string "16-color logo .ppm file"
> @@ -55,8 +65,13 @@ config LOGO_LINUX_VGA16_FILE
> -remap drivers/video/logo/clut_vga16.ppm destination.ppm
>
> config LOGO_LINUX_CLUT224
> - bool "Standard 224-color Linux logo"
> + bool "224-color Linux logo"
> default y
> + help
> + Include a 224-color Linux logo.
> + This logo can be shown on displays that support showing a palette of
> + 256 or more colors.
> + Say Y to show a logo on colorful displays.
Same, if supported, it takes precedence on the two other logo types.
> config LOGO_LINUX_CLUT224_FILE
> string "224-color logo .ppm file"
Yours sincerely,
Vincent Mailhol
prev parent reply other threads:[~2026-09-23 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 9:09 Geert Uytterhoeven
2026-09-23 11:23 ` Vincent Mailhol [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=385341aa-db86-4f22-851f-85c0e6a0ca89@kernel.org \
--to=mailhol@kernel.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®