linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] tools/csr_usb: Fix compilation failure
Date: Tue, 05 Sep 2017 10:53:29 +0200	[thread overview]
Message-ID: <1504601609.5928.3.camel@hadess.net> (raw)
In-Reply-To: <20170905083534.19184-1-hadess@hadess.net>

On Tue, 2017-09-05 at 10:35 +0200, Bastien Nocera wrote:
> GCC's "format-nonliteral" security check is enabled as an error in
> recent versions of Fedora. Given the reduced scope of use, mark the
> error as ignorable through pragma.
> 
> 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);
>   ^

I also ran into this, which looks suspicious:
obexd/plugins/bluetooth.c: In function 'register_profile':
obexd/plugins/bluetooth.c:310:7: error: format not a string literal, argument types not checked [-Werror=format-nonliteral]
       profile->driver->port);
       ^~~~~~~
obexd/plugins/bluetooth.c:314:7: error: format not a string literal, argument types not checked [-Werror=format-nonliteral]
       profile->driver->name);
       ^~~~~~~

  reply	other threads:[~2017-09-05  8:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05  8:35 [PATCH] tools/csr_usb: Fix compilation failure Bastien Nocera
2017-09-05  8:53 ` Bastien Nocera [this message]
2017-09-05 13:15   ` Marcel Holtmann
2017-09-05 14:44     ` Bastien Nocera
2017-09-05 11:51 ` Marcel Holtmann
2017-09-05 11:58   ` Bastien Nocera
2017-09-05 13:05     ` Marcel Holtmann
2017-09-05 14:44       ` Bastien Nocera
  -- strict thread matches above, loose matches on Subject: below --
2017-09-05 14:32 Bastien Nocera
2017-09-05 14:36 ` 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=1504601609.5928.3.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).