From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: TuteMthCD <matias.civadda2342001@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
qby140326@gmail.com, ilya.gladyshev@linux.dev,
Hans de Goede <hansg@kernel.org>,
chris@miget.com
Subject: Re: [PATCH v3 0/2] platform/x86: bitland-mifs-wmi: Fix TM2107 profile handling
Date: Wed, 21 Oct 2026 11:59:36 +0300 (EEST) [thread overview]
Message-ID: <5aaa99c0-b101-1c78-de31-bcffe071c452@linux.intel.com> (raw)
In-Reply-To: <20261020234927.121570-1-matias.civadda2342001@gmail.com>
On Tue, 20 Oct 2026, TuteMthCD wrote:
> This series fixes platform profile handling on the TIMI Redmi Book Pro 14
> 2022 (TM2107), using the quirks infrastructure from Mingyou Chen's v12
> series:
>
> https://lore.kernel.org/all/20261012133648.132363-1-qby140326@gmail.com/
>
> Both patches apply on top of all six patches of that series. The first
> fixes the response payload copy size, as pointed out by Chris. The second
> adds the TM2107 profile mapping and response-layout quirks.
>
> Changes in v3:
> - Rebase onto Mingyou Chen's complete v12 series.
> - Reuse the existing quirks infrastructure instead of introducing
> separate response handling and profile tables.
> - Add the payload copy fix as a separate patch.
>
> Tested profile switching on physical TM2107 hardware.
>
> This is my first submission using a dependent patch series.
> Please let me know if I missed anything.
>
> TuteMthCD (2):
The patch series seems to be formed okay.
HOWEVER, there's still the problem that you don't use your real name for
signing off the patches so I cannot apply them as is. Effectively, you
should use the name you use for signing paper documents/contracts/etc.
Documentation/process/submitting-patches.rst explains what it means when
you sign off a patch.
> platform/x86: bitland-mifs-wmi: Fix response payload copy size
> platform/x86: bitland-mifs-wmi: Fix TM2107 profile handling
>
> drivers/platform/x86/bitland-mifs-wmi.c | 23 ++++++++++++++++++++++-
> 1 file changed, 22 insertions(+), 1 deletion(-)
--
i.
prev parent reply other threads:[~2026-10-21 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 23:49 TuteMthCD
2026-10-20 23:49 ` [PATCH v3 1/2] platform/x86: bitland-mifs-wmi: Fix response payload copy size TuteMthCD
2026-10-21 12:36 ` Mingyou Chen
2026-10-20 23:49 ` [PATCH v3 2/2] platform/x86: bitland-mifs-wmi: Fix TM2107 profile handling TuteMthCD
2026-10-21 8:59 ` Ilpo Järvinen [this message]
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=5aaa99c0-b101-1c78-de31-bcffe071c452@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=chris@miget.com \
--cc=hansg@kernel.org \
--cc=ilya.gladyshev@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=matias.civadda2342001@gmail.com \
--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®