From: Greg KH <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Qasim Ijaz <qasdev00@gmail.com>,
linux-fpga@vger.kernel.org, stable@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Marco Pagani <marpagan@redhat.com>,
Moritz Fischer <mdf@kernel.org>,
Russ Weight <russ.weight@linux.dev>, Tom Rix <trix@redhat.com>,
Wu Hao <hao.wu@intel.com>, Xu Yilun <yilun.xu@intel.com>
Subject: Re: [PATCH] fpga: fix potential null pointer deref in fpga_mgr_test_img_load_sgt()
Date: Wed, 12 Mar 2025 16:07:15 +0100 [thread overview]
Message-ID: <2025031209-provider-docile-fbc3@gregkh> (raw)
In-Reply-To: <27efccdc-3400-46b9-9359-4b2a6c8254e9@web.de>
On Wed, Mar 12, 2025 at 02:01:48PM +0100, Markus Elfring wrote:
> …
> > zero it out. If the allocation fails then sgt will be NULL and the
> …
> failed?
>
>
> Can a summary phrase like “Prevent null pointer dereference
> in fpga_mgr_test_img_load_sgt()” be nicer?
>
> 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
next prev parent reply other threads:[~2025-03-12 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 23:45 [PATCH] fpga: fix potential null pointer deref in fpga_mgr_test_img_load_sgt() Qasim Ijaz
2025-03-12 13:01 ` Markus Elfring
2025-03-12 15:07 ` Greg KH [this message]
2025-03-16 22:00 ` Marco Pagani
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=2025031209-provider-docile-fbc3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Markus.Elfring@web.de \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marpagan@redhat.com \
--cc=mdf@kernel.org \
--cc=qasdev00@gmail.com \
--cc=russ.weight@linux.dev \
--cc=stable@vger.kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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).