From: Joe Perches <joe@perches.com>
To: Steve deRosier <derosier@gmail.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath6kl: Add __printf verification to ath6kl_dbg
Date: Fri, 31 Mar 2017 10:23:59 -0700 [thread overview]
Message-ID: <1490981039.27353.12.camel@perches.com> (raw)
In-Reply-To: <CALLGbR+szcYFdbdh_0qBS4B_X6YQvU6CDFpR-XZvc7p3zA+ZdQ@mail.gmail.com>
On Fri, 2017-03-31 at 10:19 -0700, Steve deRosier wrote:
> On Thu, Mar 30, 2017 at 3:57 PM, Joe Perches <joe@perches.com> wrote:
> > Fix fallout too.
[]
> My only question is why bother doing a format check on something
> that's going to be compiled out anyway?
To avoid introducing defects when writing new code
and not using the debugging code path.
next prev parent reply other threads:[~2017-03-31 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 22:57 [PATCH] ath6kl: Add __printf verification to ath6kl_dbg Joe Perches
2017-03-31 17:19 ` Steve deRosier
2017-03-31 17:23 ` Joe Perches [this message]
2017-03-31 17:34 ` Steve deRosier
2017-03-31 17:45 ` Joe Perches
2017-03-31 17:54 ` Steve deRosier
[not found] ` <e4556e95a5935f591fdff67c6fb2f7ef5c7fd04f.1490914618.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2017-04-13 12:43 ` Kalle Valo
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=1490981039.27353.12.camel@perches.com \
--to=joe@perches.com \
--cc=derosier@gmail.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).