From: Kalle Valo <kvalo@codeaurora.org>
To: Joey Pabalinas <joeypabalinas@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
luciano.coelho@intel.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: New sparse warning from min_t(): expression using sizeof(void)
Date: Sat, 21 Apr 2018 11:54:30 +0300 [thread overview]
Message-ID: <87604ley7t.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20180421082444.i4eyw2zxl6tipt6i@gmail.com> (Joey Pabalinas's message of "Fri, 20 Apr 2018 22:24:44 -1000")
Joey Pabalinas <joeypabalinas@gmail.com> writes:
> On Sat, Apr 21, 2018 at 10:50:51AM +0300, Kalle Valo wrote:
>> Is there any way to fix it? With ath10k I use sparse a lot and because
>> of these warnings sparse is now very annoying to use.
>
> I submitted a sparse patch [1] for this not too long ago, but in the
> meantime you can still curl the patch [2] and apply it directly to
> the v0.5.2 release to suppress the deluge of warnings (-Wpointer-arith
> is off by defaultl so no need to change any of you configurations).
>
> [1] https://lkml.org/lkml/2018/4/10/923
> [2] https://patchwork.kernel.org/patch/10334353/raw/
Perfect, thanks. Unfortunatelly I need to catch a boat and I can't test
it right now, but I'll do that on Monday.
--
Kalle Valo
next prev parent reply other threads:[~2018-04-21 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 7:50 New sparse warning from min_t(): expression using sizeof(void) Kalle Valo
2018-04-21 8:24 ` Joey Pabalinas
2018-04-21 8:54 ` Kalle Valo [this message]
2018-04-23 6:20 ` Luciano Coelho
2018-04-23 7:41 ` Joey Pabalinas
2018-04-23 14:10 ` 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=87604ley7t.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=joeypabalinas@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=torvalds@linux-foundation.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).