From: Markus Elfring <Markus.Elfring@web.de>
To: Zhang Shurong <zhang_shurong@foxmail.com>,
linux-staging@lists.linux.dev, kernel-janitors@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Dan Carpenter <error27@gmail.com>, Xu Panda <xu.panda@zte.com.cn>
Subject: Re: staging: ks7010: potential buffer overflow in ks_wlan_set_encode_ext()
Date: Mon, 10 Jul 2023 08:21:40 +0200 [thread overview]
Message-ID: <c8d9a151-67d0-a5eb-dd3c-12aaa85b5178@web.de> (raw)
In-Reply-To: <tencent_BB4124566E846A2FB6ECC0F63C5A15BE5009@qq.com>
…
>> It seems that further contributors need to become more aware about
>> (and finally adhere to) requirements from the Linux development documentation.
…
> I'm guilty of my incorrect patch format. And do I need to write another
> patch to fix this format issue?
This can be an usual consequence for the current change review
if you would really like to take provided information and advices
better into account.
Some communication parameters influence if further development ideas
will actually be picked up for desirable improvements
(also for your change suggestions).
Regards,
Markus
next prev parent reply other threads:[~2023-07-10 6:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 5:50 [PATCH] staging: ks7010: potential buffer overflow in ks_wlan_set_encode_ext() Zhang Shurong
2023-07-09 19:21 ` Markus Elfring
2023-07-09 19:42 ` Greg Kroah-Hartman
2023-07-09 19:56 ` Markus Elfring
2023-07-10 5:41 ` Zhang Shurong
2023-07-10 5:47 ` Greg Kroah-Hartman
2023-07-10 6:32 ` Markus Elfring
2023-07-10 6:21 ` Markus Elfring [this message]
2023-07-10 6:08 ` [PATCH] " Dan Carpenter
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=c8d9a151-67d0-a5eb-dd3c-12aaa85b5178@web.de \
--to=markus.elfring@web.de \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=xu.panda@zte.com.cn \
--cc=zhang_shurong@foxmail.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