Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@nxp.com>
To: "o-takashi@sakamocchi.jp" <o-takashi@sakamocchi.jp>,
	"tiwai@suse.de" <tiwai@suse.de>
Cc: Mihai Serban <mihai.serban@nxp.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"S.J. Wang" <shengjiu.wang@nxp.com>,
	Viorel Suman <viorel.suman@nxp.com>
Subject: Re: [PATCH] aplay: Fix error message when writing captured data
Date: Fri, 7 Apr 2017 13:13:40 +0000	[thread overview]
Message-ID: <1491570819.6595.12.camel@nxp.com> (raw)
In-Reply-To: <e7879bd4-2a31-2869-068f-43b828fe2b43@sakamocchi.jp>

On Vi, 2017-04-07 at 21:56 +0900, Takashi Sakamoto wrote:
> Hi,
> 
> On Apr 7 2017 21:14, Daniel Baluta wrote:
> > 
> > Write can return less then requested bytes, but we treat
> > this as an error.
> > 
> > Anyhow, errno is not updated in this case and we can end
> > up with a confusing error message.
> > 
> > For example, when there is no room to write data into the
> > output file we receive:
> > 
> > $ arecord -d 2000 -c 2 -r 192000 -f S16_LE -Dplughw:0,0 audio.wav
> > Recording WAVE '/mnt/msc/audio.wav' : Signed 16 bit Little Endian,
> > Rate
> > 192000 Hz, Stereo
> > audio.wav: No such file or directory
> > 
> > Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
> > ---
> >  aplay/aplay.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/aplay/aplay.c b/aplay/aplay.c
> > index ee480f2..9547d1b 100644
> > --- a/aplay/aplay.c
> > +++ b/aplay/aplay.c
> > @@ -3079,7 +3079,7 @@ static void capture(char *orig_name)
> >  				break;
> >  			}
> >  			if (write(fd, audiobuf, c) != c) {
> > -				perror(name);
> > +				fprintf(stderr, "Couldn't write
> > all data to %s\n", name);
> >  				in_aborting = 1;
> >  				break;
> >  			}
> I agree with this change.
> 
> A small nitpicking. This utility supports i18n with gettext. Let us
> use 
> gettext alias to the message?
> 
> $ cd alsa-utils/aplay
> $ git grep fprintf\( | wc
>       57     387    3939
> $ git grep fprintf\( | grep _\( | wc
>       37     260    2570
> 
> 

Sure, will send v2. I didn't know about the gettext alias. :)

Daniel.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2017-04-07 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 12:14 [PATCH] aplay: Fix error message when writing captured data Daniel Baluta
2017-04-07 12:56 ` Takashi Sakamoto
2017-04-07 13:13   ` Daniel Baluta [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=1491570819.6595.12.camel@nxp.com \
    --to=daniel.baluta@nxp.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=mihai.serban@nxp.com \
    --cc=o-takashi@sakamocchi.jp \
    --cc=shengjiu.wang@nxp.com \
    --cc=tiwai@suse.de \
    --cc=viorel.suman@nxp.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