From: Peter Oh <poh@codeaurora.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: "Valo, Kalle" <kvalo@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, "Oh,
Peter" <poh@qca.qualcomm.com>,
ath10k@lists.infradead.org
Subject: Re: [PATCH v3] ath10k: set MAC timestamp in management Rx frame
Date: Thu, 25 Feb 2016 11:49:55 -0800 [thread overview]
Message-ID: <56CF5AE3.70302@codeaurora.org> (raw)
In-Reply-To: <12890529.ZzYcJYx9dF@sven-edge>
Thank you!
On 02/25/2016 11:32 AM, Sven Eckelmann wrote:
> On Thursday 25 February 2016 10:53:23 Peter Oh wrote:
>>> I see new warnings:
>>>
>>> drivers/net/wireless/ath/ath10k/wmi.c:2199:16: warning: restricted
> __le32
>>> degrades to integer
>>> drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: restricted
> __le32
>>> degrades to integer
>>> drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: cast to
> restricted
>>> __le32
>>> drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: restricted
> __le32
>>> degrades to integer
>> Do I have a way to run this check before submitting a patch such as
>> checkpatch.pl?
> Looks like sparse with -D__CHECK_ENDIAN__ [1]
>
> You may also try smatch [2]
>
> Kind regards,
> Sven
>
> [1] https://www.kernel.org/doc/Documentation/sparse.txt
> [2] http://smatch.sourceforge.net/
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Peter Oh <poh@codeaurora.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: "Valo, Kalle" <kvalo@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org, "Oh,
Peter" <poh@qca.qualcomm.com>
Subject: Re: [PATCH v3] ath10k: set MAC timestamp in management Rx frame
Date: Thu, 25 Feb 2016 11:49:55 -0800 [thread overview]
Message-ID: <56CF5AE3.70302@codeaurora.org> (raw)
In-Reply-To: <12890529.ZzYcJYx9dF@sven-edge>
Thank you!
On 02/25/2016 11:32 AM, Sven Eckelmann wrote:
> On Thursday 25 February 2016 10:53:23 Peter Oh wrote:
>>> I see new warnings:
>>>
>>> drivers/net/wireless/ath/ath10k/wmi.c:2199:16: warning: restricted
> __le32
>>> degrades to integer
>>> drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: restricted
> __le32
>>> degrades to integer
>>> drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: cast to
> restricted
>>> __le32
>>> drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: restricted
> __le32
>>> degrades to integer
>> Do I have a way to run this check before submitting a patch such as
>> checkpatch.pl?
> Looks like sparse with -D__CHECK_ENDIAN__ [1]
>
> You may also try smatch [2]
>
> Kind regards,
> Sven
>
> [1] https://www.kernel.org/doc/Documentation/sparse.txt
> [2] http://smatch.sourceforge.net/
next prev parent reply other threads:[~2016-02-25 19:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 22:18 [PATCH v3] ath10k: set MAC timestamp in management Rx frame Peter Oh
2016-02-24 22:18 ` Peter Oh
2016-02-25 16:34 ` Valo, Kalle
2016-02-25 16:34 ` Valo, Kalle
2016-02-25 18:53 ` Peter Oh
2016-02-25 18:53 ` Peter Oh
2016-02-25 19:32 ` Sven Eckelmann
2016-02-25 19:32 ` Sven Eckelmann
2016-02-25 19:49 ` Peter Oh [this message]
2016-02-25 19:49 ` Peter Oh
2016-02-26 10:00 ` Valo, Kalle
2016-02-26 10:00 ` Valo, Kalle
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=56CF5AE3.70302@codeaurora.org \
--to=poh@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=poh@qca.qualcomm.com \
--cc=sven@narfation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.