From: Jonathan Cameron <jic23@kernel.org>
To: Tian Tao <tiantao6@hisilicon.com>
Cc: <tduszyns@gmail.com>, <mcoquelin.stm32@gmail.com>,
<alexandre.torgue@foss.st.com>, <linux-iio@vger.kernel.org>
Subject: Re: [PATCH drivers/iio 0/3] convert sysfs sprintf/snprintf/scnprintf to sysfs_emit
Date: Sun, 18 Apr 2021 11:06:05 +0100 [thread overview]
Message-ID: <20210418110605.5bbcdc8b@jic23-huawei> (raw)
In-Reply-To: <1618216751-1678-1-git-send-email-tiantao6@hisilicon.com>
On Mon, 12 Apr 2021 16:39:08 +0800
Tian Tao <tiantao6@hisilicon.com> wrote:
> Use the generic sysfs_emit() function to take place of
> sprintf/snprintf/scnprintf, to avoid buffer overrun.
>
> Tian Tao (3):
> iio:chemical:sps30: Convert sysfs sprintf/snprintf family to
> sysfs_emit
> iio: light: Convert sysfs sprintf/snprintf family to sysfs_emit
> iio: trigger: stm32-timer: Convert sysfs sprintf/snprintf family to
> sysfs_emit
>
> drivers/iio/chemical/sps30.c | 6 +++---
> drivers/iio/light/veml6030.c | 2 +-
> drivers/iio/trigger/stm32-timer-trigger.c | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
Series applied to the togreg branch of iio.git and pushed out as testing
to let the autobuilders see if they can find anything we missed.
This won't got upstream until after the merge window so plenty of time
for others to take a look if they want to.
Thanks,
Jonathan
>
prev parent reply other threads:[~2021-04-18 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 8:39 [PATCH drivers/iio 0/3] convert sysfs sprintf/snprintf/scnprintf to sysfs_emit Tian Tao
2021-04-12 8:39 ` [PATCH drivers/iio 1/3] iio:chemical:sps30: Convert sysfs sprintf/snprintf family " Tian Tao
2021-04-12 8:39 ` [PATCH drivers/iio 2/3] iio: light: " Tian Tao
2021-04-12 8:39 ` [PATCH drivers/iio 3/3] iio: trigger: stm32-timer: " Tian Tao
2021-04-18 10:06 ` Jonathan Cameron [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=20210418110605.5bbcdc8b@jic23-huawei \
--to=jic23@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=linux-iio@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=tduszyns@gmail.com \
--cc=tiantao6@hisilicon.com \
/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