From: Luke Jones <luke@ljones.dev>
To: hqp1203hqp@163.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: fix keyboard not working under some laptops
Date: Sun, 30 Apr 2023 10:36:27 +1200 [thread overview]
Message-ID: <RSEWTR.AGD3LFFAJV9D@ljones.dev> (raw)
In-Reply-To: <FLEWTR.R6BA7U7SGOH71@ljones.dev>
Hi
Additionally the patch isn't generated correctly.
In your main git of Linux kernel where the last commit is your patch do
`git format-patch HEAD^`
You should then end up with
0001-drivers-fix-keyboard-not-working-under-some-laptops.patch
On Sun, Apr 30 2023 at 10:32:03 +1200, Luke Jones <luke@ljones.dev>
wrote:
> Hi,
>
> Because this is a quirk sepcific to the FA507NV:
>
> > + .matches = {
> > + DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> > + DMI_MATCH(DMI_BOARD_NAME, "FA507NV"),
> > + },
>
> perhaps the patch title should be renamed to reflect that?
>
> I have a user with the same issue, I will confirm it fixes the
> problem.
>
next prev parent reply other threads:[~2023-04-29 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 22:32 [PATCH] drivers: fix keyboard not working under some laptops Luke Jones
2023-04-29 22:36 ` Luke Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-14 14:30 hqp1203
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=RSEWTR.AGD3LFFAJV9D@ljones.dev \
--to=luke@ljones.dev \
--cc=hqp1203hqp@163.com \
--cc=linux-kernel@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