From: Greg KH <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: vulab@iscas.ac.cn, brcm80211-dev-list.pdl@broadcom.com,
brcm80211@lists.linux.dev, linux-wireless@vger.kernel.org,
stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
Erick Archer <erick.archer@outlook.com>,
Jacobe Zang <jacobe.zang@wesion.com>,
Kalle Valo <kvalo@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: Re: [PATCH v2] brcm80211: fmac: Add error handling forbrcmf_usb_dl_writeimage()
Date: Tue, 15 Apr 2025 13:43:13 +0200 [thread overview]
Message-ID: <2025041507-proclaim-frigidity-da8c@gregkh> (raw)
In-Reply-To: <af72dff7-8ad1-476f-81f2-6f7d76761b12@web.de>
On Tue, Apr 15, 2025 at 01:21:23PM +0200, Markus Elfring wrote:
> …
> > brcmf_usb_dl_cmd() but dose not check its return value. The
> > 'state.state' and the 'state.bytes' are uninitialized if the
> …
>
> Would you ever like to benefit any more from change descriptions
> which may contain text lines that would occasionally be longer
> than 60 characters?
>
> 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-15 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 7:20 [PATCH v2] brcm80211: fmac: Add error handling forbrcmf_usb_dl_writeimage() Wentao Liang
2025-04-15 11:21 ` Markus Elfring
2025-04-15 11:43 ` 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=2025041507-proclaim-frigidity-da8c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Markus.Elfring@web.de \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=christophe.jaillet@wanadoo.fr \
--cc=erick.archer@outlook.com \
--cc=jacobe.zang@wesion.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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