linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Tissoires <bentiss@kernel.org>
To: "Limonciello, Mario" <mario.limonciello@amd.com>
Cc: Friedrich Vock <friedrich.vock@gmx.de>,
	linux-input@vger.kernel.org, "Natikar,
	Basavaraj" <Basavaraj.Natikar@amd.com>,
	"S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] HID: i2c-hid: Block a rogue device on ASUS TUF A16
Date: Mon, 3 Jul 2023 10:23:43 +0200	[thread overview]
Message-ID: <hqddkr2cqzzwxkse6tlfusm6ww4ijmeh34rwij56njlzxdmpu3@cmq5h36ia2bf> (raw)
In-Reply-To: <9c10f6f2-b145-db5e-ebed-981222a72be7@amd.com>


On Jun 30 2023, Limonciello, Mario wrote:
[...]
> 
> Friderich and some people on CC are already aware of this, but mostly for
> Benjamin and Jiri I wanted to let you know that the additional register
> fetching comparing Windows and Linux allowed me to come up with a proper
> root cause.
> 
> This series has been sent out to fix the issue properly.

Great, thanks for the heads up :)

Cheers,
Benjamin


> 
> https://lore.kernel.org/linux-gpio/20230630194716.6497-1-mario.limonciello@amd.com/

      reply	other threads:[~2023-07-03  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 15:40 [PATCH] HID: i2c-hid: Block a rogue device on ASUS TUF A16 Friedrich Vock
2023-06-02 18:43 ` Limonciello, Mario
2023-06-15 12:41   ` Friedrich Vock
2023-06-19  3:05     ` Mario Limonciello
2023-06-26 15:10       ` Limonciello, Mario
2023-06-27 14:38         ` Friedrich Vock
2023-06-30 19:55           ` Limonciello, Mario
2023-07-03  8:23             ` Benjamin Tissoires [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=hqddkr2cqzzwxkse6tlfusm6ww4ijmeh34rwij56njlzxdmpu3@cmq5h36ia2bf \
    --to=bentiss@kernel.org \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=friedrich.vock@gmx.de \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=mario.limonciello@amd.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).