public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Mailhol <mailhol@kernel.org>
To: Markus Reichelt <ml@mareichelt.com>
Cc: Helge Deller <deller@gmx.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/6] video/logo: allow custom boot logo and simplify logic
Date: Fri, 2 Jan 2026 18:18:45 +0100	[thread overview]
Message-ID: <71446537-a2a0-4051-8e4d-20256bf17824@kernel.org> (raw)
In-Reply-To: <20260102163053.GE26548@pc21.mareichelt.com>

On 02/01/2026 at 17:30, Markus Reichelt wrote:
> * Vincent Mailhol <mailhol@kernel.org> wrote:
> 
>> This series allows the user to replace the default kernel boot logo by
>> a custom one directly in the kernel configuration. This makes it
>> easier to customise the boot logo without the need to modify the
>> sources and allows such customisation to remain persistent after
>> applying the configuration to another version of the kernel.
> 
> Hah! What I have been doing for so many moons is to just cp my own logo
> 'logo_linux_clut224.ppm' -> 'drivers/video/logo/logo_linux_clut224.ppm'
> for each custom kernel build - that works like a charm.
> Maybe... I'm too pragmatic? It's that famous 'kill bill' logo from ages
> ago, 224 colors PPM

I was doing the same! I then started a rework a couple years ago to
implement this idea.. At that time, I was less experienced and did not
fully understood Kbuild. The result worked but was ugly and stayed in my
local tree.

This winter holidays, I had a bit of free time, revisited my old idea,
and this time, found something I thought was worth upstreaming. Thus
this series.

> Haven't tested your patch series cos stuff just works for me.
> Looking forward to feedback from all those logo nerds out there.

Looking forward for your Tested-by tag!


Yours sincerely,
Vincent Mailhol


  reply	other threads:[~2026-01-02 17:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 22:19 [PATCH 0/6] video/logo: allow custom boot logo and simplify logic Vincent Mailhol
2025-12-30 22:20 ` [PATCH 1/6] video/logo: remove orphan .pgm Makefile rule Vincent Mailhol
2026-01-02 16:34   ` David Heidelberg
2026-01-02 17:13     ` Vincent Mailhol
2026-01-02 17:18       ` David Heidelberg
2026-01-02 17:25         ` Vincent Mailhol
2026-01-02 19:59           ` Helge Deller
2026-01-02 20:20             ` Vincent Mailhol
2026-01-02 20:26             ` David Heidelberg
2025-12-30 22:20 ` [PATCH 2/6] video/logo: add a type parameter to the logo makefile function Vincent Mailhol
2025-12-30 22:20 ` [PATCH 3/6] video/logo: allow custom logo Vincent Mailhol
2025-12-30 22:20 ` [PATCH 4/6] newport_con: depend on LOGO_LINUX_CLUT224 instead of LOGO_SGI_CLUT224 Vincent Mailhol
2026-01-02 21:54   ` Vincent Mailhol
2025-12-30 22:20 ` [PATCH 5/6] sh: defconfig: remove CONFIG_LOGO_SUPERH_* Vincent Mailhol
2025-12-30 22:20 ` [PATCH 6/6] video/logo: move logo selection logic to Kconfig Vincent Mailhol
2026-01-01 13:17   ` Vincent Mailhol
2025-12-30 23:19 ` [PATCH 0/6] video/logo: allow custom boot logo and simplify logic John Paul Adrian Glaubitz
2025-12-31  6:46   ` Vincent Mailhol
2026-01-02 16:30 ` Markus Reichelt
2026-01-02 17:18   ` Vincent Mailhol [this message]
2026-01-02 19:55     ` Vincent Mailhol

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=71446537-a2a0-4051-8e4d-20256bf17824@kernel.org \
    --to=mailhol@kernel.org \
    --cc=dalias@libc.org \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=ml@mareichelt.com \
    --cc=ysato@users.sourceforge.jp \
    /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