From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
Cc: Mohammed Shafi Shajakhan <mohammed@codeaurora.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH v1 3/3] ath10k: Enable parsing per station rx duration for 10.4
Date: Thu, 24 Mar 2016 06:51:18 +0000 [thread overview]
Message-ID: <87d1qke5cq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <ec91f62c5b2a4c59b72df074d6ba37f0@aphydexm01b.ap.qualcomm.com> (Mohammed Shafi Shajakhan's message of "Wed, 23 Mar 2016 13:08:32 +0000")
"Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
writes:
> I will make sure, I will run sparse before sending it for review
> http://linuxwireless.org/en/users/Drivers/ath10k/CodingStyle/#Linux_style
>
> make drivers/net/wireless/ath/ath10k/ C=2 CF="-D__CHECK_ENDIAN__"
>
> regret the inconvenience so caused (including the compilation error)
I guess easier is to use my ath10k-check script:
https://github.com/qca/qca-swiss-army-knife/blob/master/tools/scripts/ath10k/ath10k-check
I use that script to test every patch before I commit them. Run the
script on the top level kernel source tree and ideally you should not
see any warnings (the output should be empty).
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
Cc: Mohammed Shafi Shajakhan <mohammed@codeaurora.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH v1 3/3] ath10k: Enable parsing per station rx duration for 10.4
Date: Thu, 24 Mar 2016 06:51:18 +0000 [thread overview]
Message-ID: <87d1qke5cq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <ec91f62c5b2a4c59b72df074d6ba37f0@aphydexm01b.ap.qualcomm.com> (Mohammed Shafi Shajakhan's message of "Wed, 23 Mar 2016 13:08:32 +0000")
"Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
writes:
> I will make sure, I will run sparse before sending it for review
> http://linuxwireless.org/en/users/Drivers/ath10k/CodingStyle/#Linux_style
>
> make drivers/net/wireless/ath/ath10k/ C=2 CF="-D__CHECK_ENDIAN__"
>
> regret the inconvenience so caused (including the compilation error)
I guess easier is to use my ath10k-check script:
https://github.com/qca/qca-swiss-army-knife/blob/master/tools/scripts/ath10k/ath10k-check
I use that script to test every patch before I commit them. Run the
script on the top level kernel source tree and ideally you should not
see any warnings (the output should be empty).
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-03-24 6:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 12:43 [PATCH v1 1/3] ath10k: Enable debugfs provision to enable Peer Stats feature Mohammed Shafi Shajakhan
2016-03-16 12:43 ` Mohammed Shafi Shajakhan
2016-03-16 12:43 ` [PATCH v1 2/3] ath10k: Introduce Extended Resource Config support for 10.4 Mohammed Shafi Shajakhan
2016-03-16 12:43 ` Mohammed Shafi Shajakhan
2016-03-16 12:43 ` [PATCH v1 3/3] ath10k: Enable parsing per station rx duration " Mohammed Shafi Shajakhan
2016-03-16 12:43 ` Mohammed Shafi Shajakhan
2016-03-23 13:00 ` Valo, Kalle
2016-03-23 13:00 ` Valo, Kalle
2016-03-23 13:03 ` Mohammed Shafi Shajakhan
2016-03-23 13:03 ` Mohammed Shafi Shajakhan
2016-03-23 13:08 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
2016-03-23 13:08 ` Shajakhan, Mohammed Shafi (Mohammed Shafi)
2016-03-24 6:51 ` Valo, Kalle [this message]
2016-03-24 6:51 ` Valo, Kalle
2016-03-24 7:01 ` Mohammed Shafi Shajakhan
2016-03-24 7:01 ` Mohammed Shafi Shajakhan
2016-04-04 14:54 ` [PATCH v1 1/3] ath10k: Enable debugfs provision to enable Peer Stats feature Valo, Kalle
2016-04-04 14:54 ` 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=87d1qke5cq.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mohammed@codeaurora.org \
--cc=mohammed@qti.qualcomm.com \
/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.