mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Musaev Ibragim <atomicus.xyz@gmail.com>
To: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Cc: Gladyshev Ilya <foxido@foxido.dev>,
	Hans de Goede <hansg@kernel.org>,
	Mingyou Chen <qby140326@gmail.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: redmi-wmi: report EC state change events
Date: Tue, 21 Jul 2026 23:31:25 +0600	[thread overview]
Message-ID: <178465508554.4674.15793036730807770065@gmail.com> (raw)
In-Reply-To: <0dccec1c-d0f2-f043-3176-728c53791f3d@linux.intel.com>

On Tue, 21 Jul 2026, Ilpo Järvinen wrote:

> Like you've now noticed (I think), there's another series attempting to
> fix the GUID problem.
>
> I'd primarily prefer taking the GUID problem fixing series (but it
> should make sure this too is addressed).
>
> If the GUID problem series not finished in this cycle, I can consider this
> patch instead towards the end of the cycle.
>
> Is that fine with you?

Yes, that's fine with me -- landing the GUID-fix series first makes
sense. I've already reviewed the Redmibook side of it on my TM2209 and
left comments on patch 2/4, including a request to keep these EC state
events observable rather than KE_IGNOREd. Happy to test v2 on this
hardware.

If the series misses the cycle, picking this patch up at the end of it
works for me.

Thanks,
Ibragim

  reply	other threads:[~2026-07-21 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 18:45 Musaev Ibragim
2026-07-21 16:47 ` Ilpo Järvinen
2026-07-21 17:31   ` Musaev Ibragim [this message]
2026-08-18 14:33 ` Ilpo Järvinen

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=178465508554.4674.15793036730807770065@gmail.com \
    --to=atomicus.xyz@gmail.com \
    --cc=foxido@foxido.dev \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=qby140326@gmail.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®