From: Greg KH <gregkh@linuxfoundation.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] serial: 8250_aspeed_vuart: Replace snprintf in show functions with sysfs_emit
Date: Wed, 10 Nov 2021 09:10:46 +0100 [thread overview]
Message-ID: <YYt+hmfOPSDg0NVM@kroah.com> (raw)
In-Reply-To: <20211110024028.135887-1-yao.jing2@zte.com.cn>
On Wed, Nov 10, 2021 at 02:40:28AM +0000, cgel.zte at gmail.com wrote:
> From: Jing Yao <yao.jing2@zte.com.cn>
>
> coccicheck complains about the use of snprintf() in sysfs show
> functions:
> WARNING use scnprintf or sprintf
>
> Use sysfs_emit instead of scnprintf, snprintf or sprintf makes more
> sense.
Same subject and changelog comments as the staging driver change you
sent in :(
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: cgel.zte@gmail.com
Cc: johan@kernel.org, jirislaby@kernel.org, joel@jms.id.au,
andrew@aj.id.au, zev@bewilderbeest.net, yao.jing2@zte.com.cn,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] serial: 8250_aspeed_vuart: Replace snprintf in show functions with sysfs_emit
Date: Wed, 10 Nov 2021 09:10:46 +0100 [thread overview]
Message-ID: <YYt+hmfOPSDg0NVM@kroah.com> (raw)
In-Reply-To: <20211110024028.135887-1-yao.jing2@zte.com.cn>
On Wed, Nov 10, 2021 at 02:40:28AM +0000, cgel.zte@gmail.com wrote:
> From: Jing Yao <yao.jing2@zte.com.cn>
>
> coccicheck complains about the use of snprintf() in sysfs show
> functions:
> WARNING use scnprintf or sprintf
>
> Use sysfs_emit instead of scnprintf, snprintf or sprintf makes more
> sense.
Same subject and changelog comments as the staging driver change you
sent in :(
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: cgel.zte@gmail.com
Cc: johan@kernel.org, jirislaby@kernel.org, joel@jms.id.au,
andrew@aj.id.au, zev@bewilderbeest.net, yao.jing2@zte.com.cn,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] serial: 8250_aspeed_vuart: Replace snprintf in show functions with sysfs_emit
Date: Wed, 10 Nov 2021 09:10:46 +0100 [thread overview]
Message-ID: <YYt+hmfOPSDg0NVM@kroah.com> (raw)
In-Reply-To: <20211110024028.135887-1-yao.jing2@zte.com.cn>
On Wed, Nov 10, 2021 at 02:40:28AM +0000, cgel.zte@gmail.com wrote:
> From: Jing Yao <yao.jing2@zte.com.cn>
>
> coccicheck complains about the use of snprintf() in sysfs show
> functions:
> WARNING use scnprintf or sprintf
>
> Use sysfs_emit instead of scnprintf, snprintf or sprintf makes more
> sense.
Same subject and changelog comments as the staging driver change you
sent in :(
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-10 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 2:40 [PATCH] serial: 8250_aspeed_vuart: Replace snprintf in show functions with sysfs_emit cgel.zte
2021-11-10 2:40 ` cgel.zte
2021-11-10 2:40 ` cgel.zte
2021-11-10 8:10 ` Greg KH [this message]
2021-11-10 8:10 ` Greg KH
2021-11-10 8:10 ` Greg KH
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=YYt+hmfOPSDg0NVM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-aspeed@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.