public inbox for linux-fbdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Mailhol <mailhol@kernel.org>
To: 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>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-fbdev@vger.kernel.org,  dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,  linux-sh@vger.kernel.org,
	linux-m68k@lists.linux-m68k.org,
	 Vincent Mailhol <mailhol@kernel.org>
Subject: [PATCH v3 1/7] video/logo: remove orphan .pgm Makefile rule
Date: Thu, 08 Jan 2026 20:04:49 +0100	[thread overview]
Message-ID: <20260108-custom-logo-v3-1-5a7aada7a6d4@kernel.org> (raw)
In-Reply-To: <20260108-custom-logo-v3-0-5a7aada7a6d4@kernel.org>

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.

Signed-off-by: Vincent Mailhol <mailhol@kernel.org>
---
 drivers/video/logo/Makefile | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/drivers/video/logo/Makefile b/drivers/video/logo/Makefile
index 895c60b8402e..8b67c4941a4c 100644
--- a/drivers/video/logo/Makefile
+++ b/drivers/video/logo/Makefile
@@ -30,8 +30,5 @@ $(obj)/%.c: $(src)/%.pbm $(obj)/pnmtologo FORCE
 $(obj)/%.c: $(src)/%.ppm $(obj)/pnmtologo FORCE
 	$(call if_changed,logo)
 
-$(obj)/%.c: $(src)/%.pgm $(obj)/pnmtologo FORCE
-	$(call if_changed,logo)
-
 # generated C files
-targets += *_mono.c *_vga16.c *_clut224.c *_gray256.c
+targets += *_mono.c *_vga16.c *_clut224.c

-- 
2.52.0


  reply	other threads:[~2026-01-08 19:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 19:04 [PATCH v3 0/7] video/logo: allow custom boot logo and simplify logic Vincent Mailhol
2026-01-08 19:04 ` Vincent Mailhol [this message]
2026-01-09  8:40   ` [PATCH v3 1/7] video/logo: remove orphan .pgm Makefile rule Geert Uytterhoeven
2026-01-09 10:48     ` Vincent Mailhol
2026-01-09 10:51       ` Geert Uytterhoeven
2026-01-08 19:04 ` [PATCH v3 2/7] video/logo: add a type parameter to the logo makefile function Vincent Mailhol
2026-01-08 19:04 ` [PATCH v3 3/7] video/logo: allow custom logo Vincent Mailhol
2026-01-08 19:04 ` [PATCH v3 4/7] newport_con: depend on LOGO_LINUX_CLUT224 instead of LOGO_SGI_CLUT224 Vincent Mailhol
2026-01-08 19:04 ` [PATCH v3 5/7] sh: defconfig: remove CONFIG_LOGO_SUPERH_* Vincent Mailhol
2026-01-08 19:04 ` [PATCH v3 6/7] video/logo: remove logo_mac_clut224 Vincent Mailhol
2026-01-09  7:28   ` Daniel Palmer
2026-01-08 19:04 ` [PATCH v3 7/7] video/logo: move logo selection logic to Kconfig Vincent Mailhol
2026-01-11 18:59 ` [PATCH v3 0/7] video/logo: allow custom boot logo and simplify logic Helge Deller

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=20260108-custom-logo-v3-1-5a7aada7a6d4@kernel.org \
    --to=mailhol@kernel.org \
    --cc=dalias@libc.org \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.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-m68k@lists.linux-m68k.org \
    --cc=linux-sh@vger.kernel.org \
    --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