From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bartosz Markowski <bartosz.markowski@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 4/4] ath10k: add QCA9377 hw1.0 support
Date: Wed, 4 Nov 2015 19:53:45 +0200 [thread overview]
Message-ID: <87lhadbqhi.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1446638015-23310-5-git-send-email-bartosz.markowski@tieto.com> (Bartosz Markowski's message of "Wed, 4 Nov 2015 12:53:35 +0100")
Bartosz Markowski <bartosz.markowski@tieto.com> writes:
> Add new BMI target version and chip id revision. Register it
> on supported chips list.
>
> Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com>
This one has whitespace issues:
drivers/net/wireless/ath/ath10k/core.c:163: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:163: please, no spaces at the start of a line
drivers/net/wireless/ath/ath10k/core.c:164: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:164: please, no spaces at the start of a line
drivers/net/wireless/ath/ath10k/core.c:165: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:165: please, no spaces at the start of a line
drivers/net/wireless/ath/ath10k/core.c:166: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:166: please, no spaces at the start of a line
drivers/net/wireless/ath/ath10k/core.c:167: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:167: please, no spaces at the start of a line
drivers/net/wireless/ath/ath10k/core.c:168: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:168: please, no spaces at the start of a line
drivers/net/wireless/ath/ath10k/core.c:169: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:169: please, no spaces at the start of a line
drivers/net/wireless/ath/ath10k/core.c:170: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:170: please, no spaces at the start of a line
drivers/net/wireless/ath/ath10k/core.c:171: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:171: please, no spaces at the start of a line
drivers/net/wireless/ath/ath10k/core.c:172: code indent should use tabs where possible
drivers/net/wireless/ath/ath10k/core.c:172: please, no spaces at the start of a line
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-11-04 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 11:53 [PATCH 0/4] update ath10k support for QCA9377 chips Bartosz Markowski
2015-11-04 11:53 ` [PATCH 1/4] ath10k: fix the currently supported QCA9377 target version name Bartosz Markowski
2015-11-04 11:53 ` [PATCH 2/4] ath10k: update missing hw_params of QCA9377 hw1.1 Bartosz Markowski
2015-11-04 11:53 ` [PATCH 3/4] ath10k: introduce dev_id to hw_params Bartosz Markowski
2015-11-04 11:53 ` [PATCH 4/4] ath10k: add QCA9377 hw1.0 support Bartosz Markowski
2015-11-04 17:53 ` Kalle Valo [this message]
2015-11-05 8:54 ` Bartosz Markowski
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=87lhadbqhi.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=bartosz.markowski@tieto.com \
--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