All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Helge Deller <deller@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [GIT PULL] fbdev late fixes for v6.12-rc5
Date: Fri, 25 Oct 2024 21:35:57 +0200	[thread overview]
Message-ID: <e3debf69-0507-41bd-999c-b3de79c809b5@gmx.de> (raw)
In-Reply-To: <CAHk-=wjKouRizUF97ZABtCmijjKR+sAOmWA4uiYhhSOwhxCT3w@mail.gmail.com>

Hi Linus,

On 10/25/24 20:31, Linus Torvalds wrote:
> On Fri, 25 Oct 2024 at 09:04, Helge Deller <deller@kernel.org> wrote:
>>
>> It's mostly about build warning fixes with cornercase CONFIG settings
>> and one big patch which removes the now unused da8xx fbdev driver.
>
> So I pulled this, but only later noticed that some of the Kconfig
> "fixes" are anything but.
>
> At least commit 447794e44744 ("fbdev: sstfb: Make CONFIG_FB_DEVICE
> optional") is not fixing anything, and very questionable.
>
> For no reason at all does it seem to enable 30-year old hardware in a
> new configuration.
>
> There were no build issues before, the build issues that existed were
> *introduced* by broken early versions of this patch.

That patch was the one I meant with "fixes [for] cornercase CONFIG settings".
But you are right that there aren't any issues fixed by this patch.

> Does anybody even *have* that hardware?

I do have a few of those (Voodoo2). Actually one is built-into one of my parisc
machines.

> Why were those pointless changes made?

When I accepted this patch I did not find it useless.
Maybe there are people who really enables Voodoo driver although
they prefer DRM. Maybe they don't even know the difference.
I applied it because I don't want compilation to fail at all
(which I see I was wrong in).

> Sure, the Voodoo1 was the bomb back in 1996 if you wanted to run
> hw-accelerated Quake, but in 2024, this change should have had more
> explanation for why anybody would care about the CONFIG_FB_DEVICE
> dependency.

Ok.

Btw, you will be astonished if you check the prices of those cards
on ebay nowadays.

> And in no case should it have been marked as a "fix".

Ok.
Do you want me to send a revert for this specific patch?

FWIW, just a few hours before I sent the pull request I did complain
about a similar patch (which I did not apply):
https://lore.kernel.org/linux-fbdev/7aabca78-dd34-4819-8a63-105d1a4cb4ba@gmx.de/T/#m070c6ba1047d26b856b0d6ac43592fc7b6f95518

Helge

  reply	other threads:[~2024-10-25 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 16:04 [GIT PULL] fbdev late fixes for v6.12-rc5 Helge Deller
2024-10-25 18:10 ` pr-tracker-bot
2024-10-25 18:31 ` Linus Torvalds
2024-10-25 19:35   ` Helge Deller [this message]
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=e3debf69-0507-41bd-999c-b3de79c809b5@gmx.de \
    --to=deller@gmx.de \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.