From: Takashi Iwai <tiwai@suse.de>
To: Prashant Malani <pmalani@chromium.org>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [PATCH 1/1] seq: arecordmidi: Add num-events option
Date: Mon, 11 Feb 2019 09:14:58 +0100 [thread overview]
Message-ID: <s5h7ee67nct.wl-tiwai@suse.de> (raw)
In-Reply-To: <CACeCKaf2w5xEW4hHxGQ7jbzKHwfQYRJ7gud9p8jEkVVV=Zq3Vg@mail.gmail.com>
On Mon, 11 Feb 2019 05:23:36 +0100,
Prashant Malani wrote:
>
> Friendly ping.
Since no one raised objection, I applied now.
thanks,
Takashi
> On Mon, Feb 4, 2019 at 12:20 PM Prashant Malani <pmalani@chromium.org>
> wrote:
>
> > Friendly ping. Sounds like Clemens mentioned atoi() should be OK (given
> > his explanation regarding non-numeric strings, along with consistency with
> > the rest of the utility).
> > Are there any other concerns with this patchset?
> >
> > Thanks once again for taking the time to review.
> >
> > Best regards,
> >
> > On Tue, Jan 29, 2019 at 3:42 PM Prashant Malani <pmalani@chromium.org>
> > wrote:
> >
> >> Interesting. Thanks for pointing that out, Clemens.
> >>
> >> In any case, I've sent both versions (atoi v/s strtol), so whichever one
> >> is preferred can be used (would be slightly inclined towards atoi, since
> >> it's used elsewhere in the file, and because of Clemens' comment;
> >> additionally, there is less code duplication with the atoi version).
> >>
> >> Best regards,
> >>
> >> On Tue, Jan 29, 2019 at 8:19 AM Clemens Ladisch <clemens@ladisch.de>
> >> wrote:
> >>
> >>> Takashi Sakamoto wrote:
> >>> > When parsing string with non-numeric characters, the behaviour of
> >>> > atoi() is undefined still in C11.
> >>>
> >>> A completely non-numeric string is specified to return zero.
> >>>
> >>> The behaviour is undefined only if the value cannot be represented, i.e.,
> >>> if it overflows.
> >>>
> >>>
> >>> Regards,
> >>> Clemens
> >>>
> >>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2019-02-11 8:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 1:44 [PATCH 1/1] seq: arecordmidi: Add num-events option pmalani
2019-01-29 3:36 ` Takashi Sakamoto
2019-01-29 5:34 ` Prashant Malani
2019-01-29 8:45 ` Takashi Sakamoto
2019-01-29 9:58 ` pmalani
2019-01-29 16:18 ` Clemens Ladisch
2019-01-29 23:42 ` Prashant Malani
2019-02-04 20:20 ` Prashant Malani
2019-02-11 4:23 ` Prashant Malani
2019-02-11 8:14 ` Takashi Iwai [this message]
2019-02-11 10:07 ` Prashant Malani
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=s5h7ee67nct.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=pmalani@chromium.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.