From: Jan Visser <starquake@linuxeverywhere.org>
To: mario.limonciello@amd.com
Cc: Basavaraj.Natikar@amd.com, Shyam-sundar.S-k@amd.com,
andriy.shevchenko@linux.intel.com, dridri85@gmail.com,
friedrich.vock@gmx.de, hdegoede@redhat.com,
linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, nmschulte@gmail.com,
npliashechnikov@gmail.com,
Jan Visser <starquake@linuxeverywhere.org>
Subject: Re: [PATCH v2 0/4] Fix for interrupt storm on ASUS TUF A16
Date: Mon, 10 Jul 2023 19:49:26 +0200 [thread overview]
Message-ID: <20230710174926.5760-1-starquake@linuxeverywhere.org> (raw)
In-Reply-To: <994042dd-9532-0dfb-8f86-98c897db75fd@amd.com>
This fixes keyboard issues on my Asus TUF Gaming A16 Advantage Edition FA617NS-N3085W
Thanks!
Tested-by: Jan Visser <starquake@linuxeverywhere.org>
prev parent reply other threads:[~2023-07-10 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 13:30 [PATCH v2 0/4] Fix for interrupt storm on ASUS TUF A16 Mario Limonciello
2023-07-05 13:30 ` [PATCH v2 1/4] pinctrl: amd: Only use special debounce behavior for GPIO 0 Mario Limonciello
2023-07-05 13:30 ` [PATCH v2 2/4] pinctrl: amd: Use amd_pinconf_set() for all config options Mario Limonciello
2023-07-06 9:16 ` Andy Shevchenko
2023-07-06 14:30 ` Limonciello, Mario
2023-07-05 13:30 ` [PATCH v2 3/4] pinctrl: amd: Drop pull up select configuration Mario Limonciello
2023-07-05 13:30 ` [PATCH v2 4/4] pinctrl: amd: Unify debounce handling into amd_pinconf_set() Mario Limonciello
2023-07-07 13:50 ` [PATCH v2 0/4] Fix for interrupt storm on ASUS TUF A16 Linus Walleij
2023-07-07 14:09 ` Limonciello, Mario
2023-07-10 17:49 ` Jan Visser [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=20230710174926.5760-1-starquake@linuxeverywhere.org \
--to=starquake@linuxeverywhere.org \
--cc=Basavaraj.Natikar@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dridri85@gmail.com \
--cc=friedrich.vock@gmx.de \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=nmschulte@gmail.com \
--cc=npliashechnikov@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;
as well as URLs for NNTP newsgroup(s).