From: Krzysztof Kozlowski <krzk@kernel.org>
To: tang.dongxing@zte.com.cn, davem@davemloft.net,
feng.wei8@zte.com.cn, shao.mingyin@zte.com.cn,
xie.ludan@zte.com.cn
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, yang.guang5@zte.com.cn,
yang.yang29@zte.com.cn, ye.xingchen@zte.com.cn,
xu.xin16@zte.com.cn
Subject: Re: [PATCH] net: atm: use sysfs_emit_at() instead of scnprintf()
Date: Mon, 17 Mar 2025 09:16:09 +0100 [thread overview]
Message-ID: <e0204a28-7e3a-48f9-aea9-20b35294ada6@kernel.org> (raw)
In-Reply-To: <20250317155102808MZdMkiovw52X0oY7n47wI@zte.com.cn>
On 17/03/2025 08:51, tang.dongxing@zte.com.cn wrote:
> From: TangDongxing <tang.dongxing@zte.com.cn>
>
> Follow the advice in Documentation/filesystems/sysfs.rst:
> show() should only use sysfs_emit() or sysfs_emit_at() when formatting
> the value to be returned to user space.
>
> Signed-off-by: TangDongxing <tang.dongxing@zte.com.cn>
Dear ZTE,
Can you slow down? You sent a bunch of emails with similar issues which
means that dozen of maintainers will deal with the same issues
independently. This looks like another vivo or huawei style submission,
leading to bugs sneaked via flood of patches.
First, fix the name used in the SoB (see submitting patches) to match
Latin transcription.
Second, use proper SoB chain, see submitting patches.
Third, really, really be sure that what you send is correct. You already
got quite responses, but you still keep sending patches.
Fourth, respond to received feedback instead of flooding us with more of
this!
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-17 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 7:51 [PATCH] net: atm: use sysfs_emit_at() instead of scnprintf() tang.dongxing
2025-03-17 8:16 ` Krzysztof Kozlowski [this message]
2025-03-17 9:09 ` tang.dongxing
2025-03-20 11:42 ` Simon Horman
2025-03-21 2:45 ` tang.dongxing
2025-03-25 15:27 ` Simon Horman
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=e0204a28-7e3a-48f9-aea9-20b35294ada6@kernel.org \
--to=krzk@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=feng.wei8@zte.com.cn \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shao.mingyin@zte.com.cn \
--cc=tang.dongxing@zte.com.cn \
--cc=xie.ludan@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=yang.guang5@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=ye.xingchen@zte.com.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