Linux Documentation
 help / color / mirror / Atom feed
From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: Angelo Dureghello <adureghello@baylibre.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Olivier Moysan" <olivier.moysan@foss.st.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] iio: dac: ad3552r-hs: add support for internal ramp
Date: Thu, 27 Mar 2025 09:09:50 -0300	[thread overview]
Message-ID: <Z-VADhMDmmPFhlC5@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <yxhvtline3ey3ekybqfe3k4y4sm6746wpqwpydxv2brryironl@u2ezr3sryqxs>

On 03/27, Angelo Dureghello wrote:
> On 26.03.2025 18:52, Marcelo Schmitt wrote:
> > Hello Angelo,
> > 
> > Patch looks good to me.
> > One minor comment bellow.
> > 
> > On 03/21, Angelo Dureghello wrote:
> > > From: Angelo Dureghello <adureghello@baylibre.com>
> > > 
...
> > > +
> > > +static ssize_t ad3552r_hs_write_data_source(struct file *f,
> > > +					    const char __user *userbuf,
> > > +					    size_t count, loff_t *ppos)
> > > +{
> > > +	struct ad3552r_hs_state *st = file_inode(f)->i_private;
> > > +	char buf[64];
> > > +	int ret;
> > > +
> > > +	ret = simple_write_to_buffer(buf, sizeof(buf) - 1, ppos, userbuf,
> > > +				     count);
> > > +	if (ret < 0)
> > > +		return ret;
> > > +
> > > +	buf[count] = 0;
> > Shouldn't it be
> > 	buf[count] = '\0';
> 
> Why ? I am zero-terminating the string properly.

Oh, okay. I was just more used to see '\0' as buffer/string terminator.
I see now buf[count] = 0; should work too.

> 
> > ?
> 
> Regards,
> angelo

Regards,
Marcelo

  reply	other threads:[~2025-03-27 12:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21 20:28 [PATCH 0/4] iio: ad3552r-hs: add support for internal ramp generator Angelo Dureghello
2025-03-21 20:28 ` [PATCH 1/4] docs: iio: add documentation for ad3552r driver Angelo Dureghello
2025-03-26 22:28   ` Marcelo Schmitt
2025-03-27  8:52     ` Angelo Dureghello
2025-03-27 12:54       ` Marcelo Schmitt
2025-03-30 16:50   ` Jonathan Cameron
2025-03-21 20:28 ` [PATCH 2/4] iio: backend: add support for data source get Angelo Dureghello
2025-03-21 20:28 ` [PATCH 3/4] iio: dac: adi-axi-dac: add " Angelo Dureghello
2025-03-28  8:15   ` Nuno Sá
2025-03-31 14:40     ` Angelo Dureghello
2025-03-21 20:28 ` [PATCH 4/4] iio: dac: ad3552r-hs: add support for internal ramp Angelo Dureghello
2025-03-26 21:52   ` Marcelo Schmitt
2025-03-27  8:56     ` Angelo Dureghello
2025-03-27 12:09       ` Marcelo Schmitt [this message]
2025-03-28  8:09         ` Nuno Sá
2025-03-28  8:28   ` Nuno Sá
2025-03-28 16:40     ` David Lechner
2025-03-30 17:01   ` Jonathan Cameron
2025-03-30 16:53 ` [PATCH 0/4] iio: ad3552r-hs: add support for internal ramp generator Jonathan Cameron
2025-03-31 19:11   ` Angelo Dureghello
2025-04-01  9:20     ` Nuno Sá

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=Z-VADhMDmmPFhlC5@debian-BULLSEYE-live-builder-AMD64 \
    --to=marcelo.schmitt1@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=adureghello@baylibre.com \
    --cc=corbet@lwn.net \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=olivier.moysan@foss.st.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