mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Vincent Mailhol <mailhol@kernel.org>, David Heidelberg <david@ixit.cz>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rich Felker <dalias@libc.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: [PATCH 1/6] video/logo: remove orphan .pgm Makefile rule
Date: Fri, 2 Jan 2026 20:59:16 +0100	[thread overview]
Message-ID: <90526885-9597-40eb-903b-7f741f87a7fc@gmx.de> (raw)
In-Reply-To: <d20c6baa-bd1f-4de7-afa7-0abb99e3bcb5@kernel.org>

On 1/2/26 18:25, Vincent Mailhol wrote:
> On 02/01/2026 at 18:18, David Heidelberg wrote:
>> On 02/01/2026 18:13, Vincent Mailhol wrote:
>>> On 02/01/2026 at 17:34, David Heidelberg wrote:
>>>> On 30/12/2025 23:20, Vincent Mailhol wrote:
>>>>> The kernel has no actual grey-scale logos. And looking at the git
>>>>> history, it seems that there never was one (or maybe there was in the
>>>>> pre-git history? I did not check that far…)
>>>>>
>>>>> Remove the Makefile rule for the .pgm grey scale images.
>>>>
>>>> Great to see this series.
>>>
>>> Thanks!
>>>
>>>> I think the Fixes: tag should still go here, even if it is not very
>>>> specific.
>>>
>>> But then, what do I put in the fixes tag? This:
>>>
>>>     Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>>>
>>> ?
>>
>> Yes
>>
>>>
>>> I am not sure it is worth bothering the stable team for something that
>>> isn't causing any real harm.
>>
>> That was my original thinking as well, but the Fixes tag is not only
>> about stable backports. It is also used for tracking, tooling, and
>> documentation, so stable picking up such patches is just one of its
>> purposes.
> 
> OK. Then why not. I added the tag in my local tree, but I will wait a
> couple days for the other review comments before sending. I will not
> spam everyone with a v3 just for that.

I like your patch!
So, I've added the v2 series to the fbdev git tree.

I don't think a "Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")" tag is
appropriate, since it doesn't fixes anything.

Let's see if issues arise due to the wider testing...

Helge

  reply	other threads:[~2026-01-02 19:59 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 [this message]
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
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=90526885-9597-40eb-903b-7f741f87a7fc@gmx.de \
    --to=deller@gmx.de \
    --cc=dalias@libc.org \
    --cc=david@ixit.cz \
    --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=mailhol@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®