From: Lukas Wunner <lukas@wunner.de>
To: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>
Cc: hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v3] apple-gmux: preserve brightness using EFI
Date: Sat, 14 Mar 2026 21:06:44 +0100 [thread overview]
Message-ID: <abW_1KU7KSVwmZ_6@wunner.de> (raw)
In-Reply-To: <20260313193956.1375-1-atharvatiwarilinuxdev@gmail.com>
On Sat, Mar 14, 2026 at 01:09:56AM +0530, Atharva Tiwari wrote:
> > Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
>
> Sorry to disturb, but its been 1 month since the patch,
> and it is still not applied. can you please apply it.
Kernel development is consensus-driven. Patches are usually not applied
as long as there are outstanding unaddressed comments. Unfortunately
you did not reply at all to the comments I offered:
https://lore.kernel.org/all/aYx6ocvaFHunfP5f@wunner.de/
Moreover patches are never applied as long as there are unaddressed
0-day build warnings:
https://lore.kernel.org/all/202602120036.rVaXQsI0-lkp@intel.com/
Please resubmit a patch which addresses the build issue and comments
you received. If you disagree with certain comments, explain why.
Thanks,
Lukas
next prev parent reply other threads:[~2026-03-14 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 9:26 [PATCH v3] apple-gmux: preserve brightness using EFI Atharva Tiwari
2026-02-11 12:01 ` Hans de Goede
2026-02-11 12:30 ` Atharva Tiwari
2026-02-11 12:32 ` Hans de Goede
2026-03-13 19:39 ` Atharva Tiwari
2026-03-14 20:06 ` Lukas Wunner [this message]
2026-02-11 12:48 ` Lukas Wunner
2026-03-14 22:45 ` Atharva Tiwari
2026-03-14 23:11 ` Armin Wolf
2026-03-15 22:08 ` Atharva Tiwari
2026-03-15 22:54 ` Armin Wolf
2026-03-16 15:37 ` Atharva Tiwari
2026-03-15 14:28 ` Lukas Wunner
2026-03-15 22:05 ` Atharva Tiwari
2026-02-11 17:03 ` kernel test robot
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=abW_1KU7KSVwmZ_6@wunner.de \
--to=lukas@wunner.de \
--cc=atharvatiwarilinuxdev@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.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