From: Takashi Iwai <tiwai@suse.de>
To: zhaoxiao <zhaoxiao@uniontech.com>
Cc: perex@perex.cz, tiwai@suse.com,
pierre-louis.bossart@linux.intel.com, lgirdwood@gmail.com,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
daniel.baluta@nxp.com, broonie@kernel.org,
guennadi.liakhovetski@linux.intel.com,
sound-open-firmware@alsa-project.org,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: intel: Replace scnprintf() calls with sysfs_emit_at()
Date: Tue, 16 Aug 2022 11:57:31 +0200 [thread overview]
Message-ID: <87wnb8y0hg.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220816085502.25295-1-zhaoxiao@uniontech.com>
On Tue, 16 Aug 2022 10:55:02 +0200,
zhaoxiao wrote:
>
> For sysfs outputs, it's safer to use a new helper, sysfs_emit(),
> instead of the raw sprintf() & co. This patch replaces the open-code
> with a new helper, sysfs_emit_at(), by passing the string offset.
Well, the function you've changed isn't used for sysfs at all...
Takashi
>
> Signed-off-by: zhaoxiao <zhaoxiao@uniontech.com>
> ---
> sound/soc/sof/intel/hda.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/sof/intel/hda.c b/sound/soc/sof/intel/hda.c
> index 6d4ecbe14adf..917d639671a7 100644
> --- a/sound/soc/sof/intel/hda.c
> +++ b/sound/soc/sof/intel/hda.c
> @@ -574,7 +574,7 @@ static void hda_dsp_dump_ext_rom_status(struct snd_sof_dev *sdev, const char *le
> chip = get_chip_info(sdev->pdata);
> for (i = 0; i < HDA_EXT_ROM_STATUS_SIZE; i++) {
> value = snd_sof_dsp_read(sdev, HDA_DSP_BAR, chip->rom_status_reg + i * 0x4);
> - len += scnprintf(msg + len, sizeof(msg) - len, " 0x%x", value);
> + len += sysfs_emit_at(msg, len, " 0x%x", value);
> }
>
> dev_printk(level, sdev->dev, "extended rom status: %s", msg);
> --
> 2.20.1
>
prev parent reply other threads:[~2022-08-16 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 8:55 zhaoxiao
2022-08-16 9:57 ` Takashi Iwai [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=87wnb8y0hg.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.com \
--cc=zhaoxiao@uniontech.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
all inboxes | Powered by JetHome®