From: Greg KH <greg@kroah.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Qasim Ijaz <qasdev00@gmail.com>,
linux-input@vger.kernel.org,
syzbot+d5204cbbdd921f1f7cad@syzkaller.appspotmail.com,
stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Jason Gerecke <jason.gerecke@wacom.com>,
Jiri Kosina <jikos@kernel.org>, Ping Cheng <ping.cheng@wacom.com>
Subject: Re: [PATCH v2] HID: wacom: fix shift OOB in kfifo allocation for zero pktlen
Date: Wed, 2 Apr 2025 09:06:06 +0100 [thread overview]
Message-ID: <2025040200-serotonin-equivocal-b264@gregkh> (raw)
In-Reply-To: <1f6f6fe9-ae81-4154-8553-dfb4ca2b1cd2@web.de>
On Wed, Apr 02, 2025 at 10:03:25AM +0200, Markus Elfring wrote:
> …
> > To fix this, we should handle cases where wacom_compute_pktlen()
> > results in 0.
>
> See also once more:
> https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.14#n94
>
> Regards,
> Markus
>
Hi,
This is the semi-friendly patch-bot of Greg Kroah-Hartman.
Markus, you seem to have sent a nonsensical or otherwise pointless
review comment to a patch submission on a Linux kernel developer mailing
list. I strongly suggest that you not do this anymore. Please do not
bother developers who are actively working to produce patches and
features with comments that, in the end, are a waste of time.
Patch submitter, please ignore Markus's suggestion; you do not need to
follow it at all. The person/bot/AI that sent it is being ignored by
almost all Linux kernel maintainers for having a persistent pattern of
behavior of producing distracting and pointless commentary, and
inability to adapt to feedback. Please feel free to also ignore emails
from them.
thanks,
greg k-h's patch email bot
prev parent reply other threads:[~2025-04-02 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 21:47 [PATCH v2] HID: wacom: fix shift OOB in kfifo allocation for zero pktlen Qasim Ijaz
2025-04-02 8:03 ` Markus Elfring
2025-04-02 8:06 ` Greg KH [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=2025040200-serotonin-equivocal-b264@gregkh \
--to=greg@kroah.com \
--cc=Markus.Elfring@web.de \
--cc=bentiss@kernel.org \
--cc=jason.gerecke@wacom.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ping.cheng@wacom.com \
--cc=qasdev00@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+d5204cbbdd921f1f7cad@syzkaller.appspotmail.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