From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] ath10k: fix recent checkpatch warnings
Date: Tue, 19 Apr 2016 15:44:21 +0000 [thread overview]
Message-ID: <87bn55k3ho.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160413111247.18823.15952.stgit@potku.adurom.net> (Kalle Valo's message of "Wed, 13 Apr 2016 14:13:08 +0300")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> I updated checkpatch and noticed that there are few new warnings.
>
> v2:
>
> * fix tests in patch 3
> * add patch 5 to fix a new warning in mac.c
>
> ---
>
> Kalle Valo (5):
> ath10k: fix checkpatch warnings related to spaces
> ath10k: prefer kernel type 'u64' over 'u_int64_t'
> ath10k: prefer ether_addr_equal() or ether_addr_equal_unaligned() over memcmp()
> ath10k: prefer ether_addr_copy() over memcpy()
> ath10k: fix parenthesis alignment
Applied.
--
Kalle Valo
prev parent reply other threads:[~2016-04-19 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 11:13 [PATCH v2 0/5] ath10k: fix recent checkpatch warnings Kalle Valo
2016-04-13 11:13 ` [PATCH v2 1/5] ath10k: fix checkpatch warnings related to spaces Kalle Valo
2016-04-14 7:47 ` Joe Perches
2016-04-13 11:13 ` [PATCH v2 2/5] ath10k: prefer kernel type 'u64' over 'u_int64_t' Kalle Valo
2016-04-13 11:13 ` [PATCH v2 3/5] ath10k: prefer ether_addr_equal() or ether_addr_equal_unaligned() over memcmp() Kalle Valo
2016-04-13 11:14 ` [PATCH v2 4/5] ath10k: prefer ether_addr_copy() over memcpy() Kalle Valo
2016-04-13 11:14 ` [PATCH v2 5/5] ath10k: fix parenthesis alignment Kalle Valo
2016-04-19 15:44 ` Valo, Kalle [this message]
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=87bn55k3ho.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@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).