From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Armin Wolf <W_Armin@gmx.de>
Cc: Hans de Goede <hansg@kernel.org>,
wse@tuxedocomputers.com, platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] platform/x86: uniwill-laptop: Lightbar fixes
Date: Thu, 15 Oct 2026 14:00:02 +0300 (EEST) [thread overview]
Message-ID: <2a516987-83a4-d703-3226-be216e499b1a@linux.intel.com> (raw)
In-Reply-To: <3a55c989-f16e-40a5-bd2c-201d45c82c85@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2692 bytes --]
On Sat, 10 Oct 2026, Armin Wolf wrote:
> Am 08.10.26 um 19:38 schrieb Ilpo Järvinen:
>
> > On Wed, 07 Oct 2026 16:38:53 +0200, Armin Wolf wrote:
> >
> > > This patch series mainly deals with various issues inside the code
> > > responsible for controlling the lightbar on supported devices.
> > >
> > > The first patch utilizes the improved multicolor LED API to report
> > > the correct brightness of the lightbar to userspace. The next two
> > > patches fix issues discovered inside the code for controlling
> > > animations, while the fourth patch fixes an issue with the naming
> > > of the LEDs in general. The last patch also adds support for another
> > > variant of the Intel NUC x15 laptop kit.
> > >
> > > [...]
> > Thank you for your contribution, it has been applied to my local
> > review-ilpo-next branch. Note it will show up in the public
> > platform-drivers-x86/review-ilpo-next branch only once I've pushed my
> > local branch there, which might take a while.
>
> Thank you :)
>
> I noticed that the LED next branch contains a commit that requires triggers
> to implement a new callback and prints a warning if this is not the case.
>
> Should i wait till the next cycle to send a patch implementing said callback
> or do you want to rebase for-next onto LED next?
...Goes to look at the other repo...
I don't want to base on top of other maintainers next branches (or pull
them into my for-next).
I suppose it might be best to make that addition after -rc1 through
fixes, or if time permits, already during the merge window in a separate
PR after the usual for-next PR.
--
i.
> Thanks,
> Armin Wolf
>
> > FYI [if applicable to your patch], as per Linus' policy change, also
> > fixes are mostly routed through for-next unless the fix is for a
> > commit introduced in the most recent cycle or is clearly a regression
> > fix.
> >
> > The list of commits applied:
> > [1/5] platform/x86: uniwill-laptop: Report correct lightbar brightness
> > commit: de41d8b4d0dbb81c81cd99c245238d878a3e1951
> > [2/5] platform/x86: uniwill-laptop: Implement rainbow animation as trigger
> > commit: 59e4e406b6c08ad41f3ad86db6d42b82d8539c12
> > [3/5] platform/x86: uniwill-laptop: Fix breathing animation on Intel QC
> > commit: 969a3bfa474e35828e142d0160f393a97d9bf0ee
> > [4/5] platform/x86: uniwill-laptop: Label multicolor LEDs correctly
> > commit: 42e6b269fc1134a3fcce57539034ee496e2c1344
> > [5/5] platform/x86: uniwill-laptop: Extend support for the Intel NUC x15
> > commit: 7a159a14ce0f5d5a3c2f835f39986ec5539ae374
> >
> > --
> > i.
> >
> >
>
--
i.
next prev parent reply other threads:[~2026-10-15 11:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 14:38 Armin Wolf
2026-10-07 14:38 ` [PATCH v2 1/5] platform/x86: uniwill-laptop: Report correct lightbar brightness Armin Wolf
2026-10-07 14:38 ` [PATCH v2 2/5] platform/x86: uniwill-laptop: Implement rainbow animation as trigger Armin Wolf
2026-10-10 11:20 ` Rong Zhang
2026-10-11 0:52 ` Armin Wolf
2026-10-11 19:47 ` Rong Zhang
2026-10-11 22:48 ` Armin Wolf
2026-10-12 13:13 ` Rong Zhang
2026-10-07 14:38 ` [PATCH v2 3/5] platform/x86: uniwill-laptop: Fix breathing animation on Intel QC Armin Wolf
2026-10-07 14:38 ` [PATCH v2 4/5] platform/x86: uniwill-laptop: Label multicolor LEDs correctly Armin Wolf
2026-10-07 14:38 ` [PATCH v2 5/5] platform/x86: uniwill-laptop: Extend support for the Intel NUC x15 Armin Wolf
2026-10-08 17:38 ` [PATCH v2 0/5] platform/x86: uniwill-laptop: Lightbar fixes Ilpo Järvinen
2026-10-10 1:22 ` Armin Wolf
2026-10-10 11:18 ` Rong Zhang
2026-10-15 11:00 ` Ilpo Järvinen [this message]
2026-10-15 20:32 ` Armin Wolf
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=2a516987-83a4-d703-3226-be216e499b1a@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=wse@tuxedocomputers.com \
/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®