From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] tools/csr_usb: Fix compilation failure
Date: Thu, 02 Nov 2017 15:11:45 +0100 [thread overview]
Message-ID: <1509631905.2869.58.camel@hadess.net> (raw)
In-Reply-To: <20171102140953.21684-1-hadess@hadess.net>
On Thu, 2017-11-02 at 15:09 +0100, Bastien Nocera wrote:
> GCC's "format-nonliteral" security check is enabled as an error in
> recent versions of Fedora. Given the limited formats, pass a boolean
> to switch between the 2 different formats.
>
> tools/csr_usb.c: In function 'read_value':
> tools/csr_usb.c:82:2: error: format not a string literal, argument
> types not checked [-Werror=format-nonliteral]
> n = fscanf(file, format, &value);
> ^
Sorry, those are re-send because of a command-line typo. They're still
applicable though.
next prev parent reply other threads:[~2017-11-02 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 14:09 [PATCH 1/2] tools/csr_usb: Fix compilation failure Bastien Nocera
2017-11-02 14:09 ` [PATCH 2/2] obex: Work-around " Bastien Nocera
2017-11-24 14:06 ` Bastien Nocera
2017-11-24 14:48 ` Luiz Augusto von Dentz
2017-11-24 15:22 ` Bastien Nocera
2017-11-02 14:11 ` Bastien Nocera [this message]
2017-11-24 14:06 ` [PATCH 1/2] tools/csr_usb: Fix " Bastien Nocera
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=1509631905.2869.58.camel@hadess.net \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).