[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <940cab8b-7e44-47dd-bfae-4c5b4236a054@kernel.org>
Date: Mon, 17 Mar 2025 09:48:18 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: xie.ludan@....com.cn, jirislaby@...nel.org
Cc: tglx@...utronix.de, linux-kernel@...r.kernel.org, xu.xin16@....com.cn,
yang.yang29@....com.cn, feng.wei8@....com.cn, xie.ludan@....com.cn,
shao.mingyin@....com.cn, xie.ludan@....com.cn, tang.dongxing@....com.cn
Subject: Re: [PATCH linux-next] genirq: use sysfs_emit()/sysfs_emit_at()
instead of scnprintf().
On 17/03/2025 09:22, xie.ludan@....com.cn wrote:
>> Are you a bot?
>
>> On 17. 03. 25, 7:54, xie.ludan@....com.cn wrote:> From: XieLudan <xie.ludan@....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
Powered by blists - more mailing lists