Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andrew Ijano <andrew.ijano@gmail.com>
Cc: andrew.lopes@alumni.usp.br, gustavobastos@usp.br,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	jstephan@baylibre.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 4/4] iio: accel: sca3000: use sysfs_emit_at() instead of sprintf()
Date: Sun, 6 Jul 2025 10:41:59 +0100	[thread overview]
Message-ID: <20250706104159.59e525ee@jic23-huawei> (raw)
In-Reply-To: <CANZih_SWg03U1jOn63++A=+_9GkzFhtK7S563hdb2m=tk5SK0A@mail.gmail.com>

On Sat, 5 Jul 2025 00:45:05 -0300
Andrew Ijano <andrew.ijano@gmail.com> wrote:

> On Sat, Jun 21, 2025 at 2:58 PM Jonathan Cameron <jic23@kernel.org> wrote:
> > > @@ -423,16 +423,16 @@ sca3000_show_available_3db_freqs(struct device *dev,
> > >  {
> > >       struct iio_dev *indio_dev = dev_to_iio_dev(dev);
> > >       struct sca3000_state *st = iio_priv(indio_dev);
> > > -     int len;
> > > +     unsigned int len = 0;  
> >
> > No need to initialize as set on the next line  
> 
> That makes sense! I´ll change that.
> 
> >  
> > >
> > > -     len = sprintf(buf, "%d", st->info->measurement_mode_3db_freq);
> > > +     len = sysfs_emit_at(buf, len, "%d", st->info->measurement_mode_3db_freq);  
> >
> > sysfs_emit() when you know you are at the start.
> >  
> Ok! Thanks.
> 
> >  
> > >       if (st->info->option_mode_1)
> > > -             len += sprintf(buf + len, " %d",
> > > +             len += sysfs_emit_at(buf, len, " %d",
> > >                              st->info->option_mode_1_3db_freq);  
> > Fix alignment.
> >  
> > >       if (st->info->option_mode_2)
> > > -             len += sprintf(buf + len, " %d",
> > > +             len += sysfs_emit_at(buf, len, " %d",
> > >                              st->info->option_mode_2_3db_freq);  
> >
> > same here.  
> 
> Actually, both cases are aligned. I checked the code and they have the
> same number of tabs, and in this email they have the same number of
> spaces.
> However, since I'm not reading this diff with a monospaced font, for
> me it appears to be different but this is caused by the difference in
> size of "-" and "+".
> Maybe this is why it appears to be different for you too?
Key as in earlier reply is parameters that need to go on an additional line
are not aligned as particular number of tabs, they are aligned to under
the parameters on the first line.

The only normal reason to break with that rule is on particularly long
lines.

Jonathan

> 
> Thanks,
> Andrew


  reply	other threads:[~2025-07-06  9:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18  3:12 [PATCH v6 0/4] iio: accel: sca3000: simplify by using newer infrastructure Andrew Ijano
2025-06-18  3:12 ` [PATCH v6 1/4] iio: accel: sca3000: replace usages of internal read data helpers by spi helpers Andrew Ijano
2025-06-21 17:38   ` Jonathan Cameron
2025-07-05  3:17     ` Andrew Ijano
2025-06-18  3:12 ` [PATCH v6 2/4] iio: accel: sca3000: clean sca3000_read_data() Andrew Ijano
2025-06-21 17:40   ` Jonathan Cameron
2025-06-18  3:12 ` [PATCH v6 3/4] iio: accel: sca3000: use lock guards Andrew Ijano
2025-06-21 17:55   ` Jonathan Cameron
2025-07-05  3:37     ` Andrew Ijano
2025-07-06  9:37       ` Jonathan Cameron
2025-06-18  3:12 ` [PATCH v6 4/4] iio: accel: sca3000: use sysfs_emit_at() instead of sprintf() Andrew Ijano
2025-06-21 17:58   ` Jonathan Cameron
2025-07-05  3:45     ` Andrew Ijano
2025-07-06  9:41       ` Jonathan Cameron [this message]
2025-06-18  5:55 ` [PATCH v6 0/4] iio: accel: sca3000: simplify by using newer infrastructure Andy Shevchenko
2025-06-18 12:24   ` Andrew Ijano
2025-06-18 17:41     ` Andy Shevchenko
2025-06-18 18:20       ` Andrew Ijano
2025-06-19 15:23         ` Andy Shevchenko
2025-07-05  3:03           ` Andrew Ijano
2025-07-05 18:18             ` Andy Shevchenko

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=20250706104159.59e525ee@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andrew.ijano@gmail.com \
    --cc=andrew.lopes@alumni.usp.br \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gustavobastos@usp.br \
    --cc=jstephan@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.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