linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] wifi: ti: Convert sprintf/snprintf to sysfs_emit
Date: Mon, 18 Mar 2024 09:42:51 +0000	[thread overview]
Message-ID: <115f3f2f-310f-4474-bdf6-070d5c30876c@fujitsu.com> (raw)
In-Reply-To: <87cyrrew7f.fsf@kernel.org>

Kalle,


On 18/03/2024 17:16, Kalle Valo wrote:
> Li Zhijian <lizhijian@fujitsu.com> writes:
> 
>> Per filesystems/sysfs.rst, show() should only use sysfs_emit()
>> or sysfs_emit_at() when formatting the value to be returned to user space.
>>
>> coccinelle complains that there are still a couple of functions that use
>> snprintf(). Convert them to sysfs_emit().
>>
>> sprintf() will be converted as weel if they have.
>>
>> Generally, this patch is generated by
>> make coccicheck M=<path/to/file> MODE=patch \
>> COCCI=scripts/coccinelle/api/device_attr_show.cocci
>>
>> No functional change intended
>>
>> CC: Kalle Valo <kvalo@kernel.org>
>> CC: linux-wireless@vger.kernel.org
>> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
>> ---
>> V2: subject updated
>>
>> This is a part of the work "Fix coccicheck device_attr_show warnings"[1]
>> Split them per subsystem so that the maintainer can review it easily
>> [1] https://lore.kernel.org/lkml/20240116041129.3937800-1-lizhijian@fujitsu.com/
>> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> 
> Please resubmit the whole patchset as v3.


May I know what's wrong with this V2? or what update should I do in V3


> Even if just one patch has changed in a patch series resubmit the whole patchset (and remember to increase the version number), do not just resubmit that one changed patch. The reason is that it's difficult to apply patches in correct order when some of them are submitted separately.

I thought I had followed this rule. Feel free to let me know if I missed something


Thanks
Zhijian

> 
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#resubmit_the_whole_patchset
> 
> 

  reply	other threads:[~2024-03-18  9:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  5:52 [PATCH v2 1/3] wifi: ath: Convert sprintf/snprintf to sysfs_emit Li Zhijian
2024-03-15  5:52 ` [PATCH v2 2/3] wifi: b43: " Li Zhijian
2024-03-21 15:08   ` Kalle Valo
2024-03-15  5:52 ` [PATCH v2 3/3] wifi: ti: " Li Zhijian
2024-03-18  9:16   ` Kalle Valo
2024-03-18  9:42     ` Zhijian Li (Fujitsu) [this message]
2024-03-18 10:05       ` Kalle Valo
2024-03-25 10:49 ` [PATCH v2 1/3] wifi: ath: " Kalle Valo

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=115f3f2f-310f-4474-bdf6-070d5c30876c@fujitsu.com \
    --to=lizhijian@fujitsu.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).