Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: alsa-devel@alsa-project.org, broonie@sirena.org.uk
Subject: Re: [alsa-tools][PATCH] Fix clang	-Wreserved-user-defined-literal warnings
Date: Tue, 24 Apr 2018 21:32:46 +0200	[thread overview]
Message-ID: <s5hr2n4wgbl.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180424192432.41355-1-raj.khem@gmail.com>

On Tue, 24 Apr 2018 21:24:32 +0200,
Khem Raj wrote:
> 
> | us428control.cc:66:18: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
> |         printf("usage: "PROGNAME" [-v verbosity_level 0..2] [-c card] [-D device] [-u usb-device] [-m mode]\n");
> |                         ^
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>

Thanks, applied now.


Takashi

      reply	other threads:[~2018-04-24 19:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 19:24 [alsa-tools][PATCH] Fix clang -Wreserved-user-defined-literal warnings Khem Raj
2018-04-24 19:32 ` Takashi Iwai [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=s5hr2n4wgbl.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=raj.khem@gmail.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