From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: ye.xingchen@zte.com.cn, lars@metafoo.de, linmq006@gmail.com,
u.kleine-koenig@pengutronix.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: magnetometer: bmc150_magn: Convert to use sysfs_emit_at() API
Date: Sun, 11 Dec 2022 12:15:06 +0000 [thread overview]
Message-ID: <20221211121506.4d694c74@jic23-huawei> (raw)
In-Reply-To: <CAHp75VfJx84-J2GdOWQAPAtMhPVS3X-dEuHYQqyP4a0WjDsgdQ@mail.gmail.com>
On Wed, 7 Dec 2022 10:46:14 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Wed, Dec 7, 2022 at 9:49 AM <ye.xingchen@zte.com.cn> wrote:
> >
> > From: ye xingchen <ye.xingchen@zte.com.cn>
> >
> > Follow the advice of the Documentation/filesystems/sysfs.rst and show()
> > should only use sysfs_emit() or sysfs_emit_at() when formatting the
> > value to be returned to user space.
>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmai.com>
>
> > Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
> > ---
> > drivers/iio/magnetometer/bmc150_magn.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/drivers/iio/magnetometer/bmc150_magn.c b/drivers/iio/magnetometer/bmc150_magn.c
> > index 06d5a1ef1fbd..1398684a7f30 100644
> > --- a/drivers/iio/magnetometer/bmc150_magn.c
> > +++ b/drivers/iio/magnetometer/bmc150_magn.c
> > @@ -598,8 +598,7 @@ static ssize_t bmc150_magn_show_samp_freq_avail(struct device *dev,
> > for (i = 0; i < ARRAY_SIZE(bmc150_magn_samp_freq_table); i++) {
> > if (bmc150_magn_samp_freq_table[i].freq > data->max_odr)
> > break;
> > - len += scnprintf(buf + len, PAGE_SIZE - len, "%d ",
> > - bmc150_magn_samp_freq_table[i].freq);
> > + len += sysfs_emit_at(buf, len, "%d ", bmc150_magn_samp_freq_table[i].freq);
> > }
I'd prefer we keep the line break before the last parameter.
Generally in IIO at least, preference is for < 80 chars except where readability is
significantly enhanced by a longer line. That's not true in this case.
Jonathan
> > /* replace last space with a newline */
> > buf[len - 1] = '\n';
> > --
> > 2.25.1
>
>
>
prev parent reply other threads:[~2022-12-11 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 7:49 ye.xingchen
2022-12-07 8:46 ` Andy Shevchenko
2022-12-11 12:15 ` 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=20221211121506.4d694c74@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=lars@metafoo.de \
--cc=linmq006@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=ye.xingchen@zte.com.cn \
/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®