All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Hans de Goede <hansg@kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	PDx86 <platform-driver-x86@vger.kernel.org>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Jiri Kosina" <jikos@kernel.org>,
	"Benjamin Tissoires" <bentiss@kernel.org>,
	"Sebastian Reichel" <sre@kernel.org>
Subject: Re: [GIT PULL] platform-drivers-x86 for v6.16-1
Date: Tue, 27 May 2025 20:16:33 +0200	[thread overview]
Message-ID: <aDYBgcSbVQriCyhO@duo.ucw.cz> (raw)
In-Reply-To: <4cac7f91-608b-4362-99ed-4d8cd5935900@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 737 bytes --]

Hi!

> > 4) We don't have reasonable support for the new API in the userland.
> 
> This is simply not true. Openrgb's next release is planning to
> include HID lamparray support.

I said "reasonable", and openrgb is not reasonable. It is the same
mess "gpm" was. Remember gpm for mouse handling? Except that... it is
bigger mess. Few megabytes bigger, IIRC, links against QT.

I have debian 11 here. That does not even have openrgb.

Device drivers in userland ... never worked too well. Openrgb is a
hardware driver that happens to link QT gui into the binary. That's
... not reasonable.

Best regards,
							Pavel
-- 
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, and Musk!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2025-05-27 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27  9:44 [GIT PULL] platform-drivers-x86 for v6.16-1 Ilpo Järvinen
2025-05-27 12:07 ` Pavel Machek
2025-05-27 12:47   ` Hans de Goede
2025-05-27 12:49     ` Hans de Goede
2025-05-27 13:13     ` Benjamin Tissoires
2025-05-27 15:02     ` Werner Sembach
2025-05-27 18:16     ` Pavel Machek [this message]
2025-05-29 17:48 ` pr-tracker-bot

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=aDYBgcSbVQriCyhO@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=andy@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=sre@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.