public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: [GIT PULL] fbdev late fixes for v6.12-rc5
Date: Fri, 25 Oct 2024 18:04:12 +0200	[thread overview]
Message-ID: <ZxvBfDuqSC_TEM78@carbonx1> (raw)

Hi Linus,

would you please pull a few late fbdev fixes ?
It's mostly about build warning fixes with cornercase CONFIG settings
and one big patch which removes the now unused da8xx fbdev driver.

Those patches have been in for-next for the last 10 days without issues
(Arnd's patch shows a later date because I added a R-b tag).

Thanks,
Helge

----------------------------------------------------------------
The following changes since commit 8e929cb546ee42c9a61d24fae60605e9e3192354:

  Linux 6.12-rc3 (2024-10-13 14:33:32 -0700)

are available in the Git repository at:

  http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git tags/fbdev-for-6.12-rc5

for you to fetch changes up to 51521d2e2c35959cc70a62ccddf694965e29c950:

  fbdev: wm8505fb: select CONFIG_FB_IOMEM_FOPS (2024-10-21 11:16:51 +0200)

----------------------------------------------------------------
fbdev fixes for 6.12-rc5:

- Fix some build warnings and failures with CONFIG_FB_IOMEM_FOPS and
  CONFIG_FB_DEVICE
- Remove the da8xx fbdev driver
- Constify struct sbus_mmap_map and fix indentation warning

----------------------------------------------------------------
Arnd Bergmann (1):
      fbdev: wm8505fb: select CONFIG_FB_IOMEM_FOPS

Bartosz Golaszewski (1):
      fbdev: da8xx: remove the driver

Christophe JAILLET (1):
      fbdev: Constify struct sbus_mmap_map

Gonzalo Silvalde Blanco (1):
      fbdev: sstfb: Make CONFIG_FB_DEVICE optional

SurajSonawane2415 (1):
      fbdev: nvidiafb: fix inconsistent indentation warning

 drivers/video/fbdev/Kconfig        |   15 +-
 drivers/video/fbdev/Makefile       |    1 -
 drivers/video/fbdev/bw2.c          |    2 +-
 drivers/video/fbdev/cg14.c         |    2 +-
 drivers/video/fbdev/cg3.c          |    2 +-
 drivers/video/fbdev/cg6.c          |    2 +-
 drivers/video/fbdev/da8xx-fb.c     | 1665 ------------------------------------
 drivers/video/fbdev/ffb.c          |    2 +-
 drivers/video/fbdev/leo.c          |    2 +-
 drivers/video/fbdev/nvidia/nv_hw.c |    8 +-
 drivers/video/fbdev/p9100.c        |    2 +-
 drivers/video/fbdev/sbuslib.c      |    2 +-
 drivers/video/fbdev/sbuslib.h      |    2 +-
 drivers/video/fbdev/sstfb.c        |    9 +-
 drivers/video/fbdev/tcx.c          |    2 +-
 include/video/da8xx-fb.h           |   94 --
 16 files changed, 22 insertions(+), 1790 deletions(-)
 delete mode 100644 drivers/video/fbdev/da8xx-fb.c
 delete mode 100644 include/video/da8xx-fb.h

             reply	other threads:[~2024-10-25 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 16:04 Helge Deller [this message]
2024-10-25 18:10 ` [GIT PULL] fbdev late fixes for v6.12-rc5 pr-tracker-bot
2024-10-25 18:31 ` Linus Torvalds
2024-10-25 19:35   ` Helge Deller
2024-10-25 20:00     ` Linus Torvalds

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=ZxvBfDuqSC_TEM78@carbonx1 \
    --to=deller@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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