From: Krzysztof Kozlowski <krzk@kernel.org>
To: xie.ludan@zte.com.cn, jirislaby@kernel.org
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
xu.xin16@zte.com.cn, yang.yang29@zte.com.cn,
feng.wei8@zte.com.cn, xie.ludan@zte.com.cn,
shao.mingyin@zte.com.cn, xie.ludan@zte.com.cn,
tang.dongxing@zte.com.cn
Subject: Re: [PATCH linux-next] genirq: use sysfs_emit()/sysfs_emit_at() instead of scnprintf().
Date: Mon, 17 Mar 2025 09:48:18 +0100 [thread overview]
Message-ID: <940cab8b-7e44-47dd-bfae-4c5b4236a054@kernel.org> (raw)
In-Reply-To: <20250317162238425-kqmo4SSrhMo3_UytWSPc@zte.com.cn>
On 17/03/2025 09:22, xie.ludan@zte.com.cn wrote:
>> Are you a bot?
>
>> On 17. 03. 25, 7:54, xie.ludan@zte.com.cn wrote:> From: XieLudan <xie.ludan@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.
>
> I'm sorry if I make any mistakes. I'm just starting to learn how to submit patches to the community and I'm still learning the proper submission process.
> I would greatly appreciate your patience and guidance during this learning phase. Thank you for your understanding!
So you decided to learn by sending 60 patches last two/three days?
Several of these contributions received feedback already but you never
responded to that.
If you want to learn, then send one patch and learn from it.
Sending 60 patches and making the same mistakes, like not even building
the code, means huge review effort on the community side.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-03-17 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 6:54 xie.ludan
2025-03-17 7:14 ` Jiri Slaby
2025-03-17 8:22 ` xie.ludan
2025-03-17 8:48 ` Krzysztof Kozlowski [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=940cab8b-7e44-47dd-bfae-4c5b4236a054@kernel.org \
--to=krzk@kernel.org \
--cc=feng.wei8@zte.com.cn \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shao.mingyin@zte.com.cn \
--cc=tang.dongxing@zte.com.cn \
--cc=tglx@linutronix.de \
--cc=xie.ludan@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@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
all inboxes | Powered by JetHome®