Linux Input/HID development
 help / color / mirror / Atom feed
From: Wei Jie LAW <98lawweijie@gmail.com>
To: killertofu@gmail.com
Cc: 98lawweijie@gmail.com, bentiss@kernel.org,
	jason.gerecke@wacom.com, jikos@kernel.org,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	ping.cheng@wacom.com, stable@vger.kernel.org
Subject: Re: [PATCH v3] HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce()
Date: Fri,  4 Sep 2026 10:02:35 +0800	[thread overview]
Message-ID: <20260904020235.8227-1-98lawweijie@gmail.com> (raw)
In-Reply-To: <CANRwn3RFVDy+y-fpLkb1mfjiKyQgp1Jg0tyBTO+G0xem2s1jkQ@mail.gmail.com>


On Thu, Sep 3, 2026 at 3:36 PM Jason Gerecke <killertofu@gmail.com> wrote:
>
> I'm still finding the above paragraph kinda hard to understand. What
> do you think of something like the following instead?

Your version is definitely easier to understand. I'm good with it!

> Other than the above language issue:
> Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com

Thanks. Should I submit a v4 patch with your "Reviewed-by" and the
updated language, or is leaving it as-is (here) just fine?

Regards,
Wei Jie

  reply	other threads:[~2026-09-04  2:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 10:31 [PATCH v2] HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() Wei Jie Law
2026-08-25 10:47 ` sashiko-bot
2026-08-27 19:02 ` Jason Gerecke
2026-08-28  3:33   ` [PATCH v3] " Wei Jie LAW
2026-08-28  3:50     ` sashiko-bot
2026-09-03 22:36     ` Jason Gerecke
2026-09-04  2:02       ` Wei Jie LAW [this message]
2026-09-08 18:14         ` Jason Gerecke
2026-09-09  1:15       ` [PATCH v4] " Wei Jie LAW
2026-09-09  1:30         ` sashiko-bot
2026-09-11 13:44         ` Jiri Kosina
2026-08-29  1:04   ` [PATCH v2] " Wei Jie Law

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=20260904020235.8227-1-98lawweijie@gmail.com \
    --to=98lawweijie@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=jason.gerecke@wacom.com \
    --cc=jikos@kernel.org \
    --cc=killertofu@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ping.cheng@wacom.com \
    --cc=stable@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