From: Kalle Valo <kvalo@codeaurora.org>
To: Sven Eckelmann <seckelmann@datto.com>
Cc: Anilkumar Kolli <akolli@codeaurora.org>,
ath11k@lists.infradead.org, John Crispin <john@phrozen.org>
Subject: Re: [PATCH] ath11k: fix compiler warnings for unused variables
Date: Mon, 15 Apr 2019 17:07:39 +0300 [thread overview]
Message-ID: <871s23cqfo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2594851.t0ysoKU8H1@bentobox> (Sven Eckelmann's message of "Wed, 10 Apr 2019 10:04:32 +0200")
Sven Eckelmann <seckelmann@datto.com> writes:
> On Wednesday, 10 April 2019 07:58:40 CEST John Crispin wrote:
>> CC [M] drivers/net/wireless/ath/ath11k/core.o
>> drivers/net/wireless/ath/ath11k/core.c: In function 'ath11k_core_init':
>> drivers/net/wireless/ath/ath11k/core.c:609:10: warning: unused
>> variable 'rproc_phandle' [-Wunused-variable]
>> phandle rproc_phandle;
>> ^
>> drivers/net/wireless/ath/ath11k/core.c:608:16: warning: unused
>> variable 'prproc' [-Wunused-variable]
>> struct rproc *prproc;
>> ^
>> drivers/net/wireless/ath/ath11k/core.c:607:17: warning: unused
>> variable 'dev' [-Wunused-variable]
>> struct device *dev = sc->dev;
>> ^
>
> This patch doesn't apply because they just dropped the
> CONFIG_IPQ_SUBSYSTEM_RESTART support (which is their only way to get the Q6 up
> in their 4.4 Hawkeye kernel) using a off-the-list patch [1] submission.
BTW, now as the ath11k mailing list is up and running, I won't apply
patches directly to ath11k-bringup branch anymore. I only take them from
this list after review, I was thinking to wait minimum two days for
comments.
--
Kalle Valo
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-04-15 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 5:58 [PATCH] ath11k: fix compiler warnings for unused variables John Crispin
2019-04-10 8:04 ` Sven Eckelmann
2019-04-15 14:07 ` Kalle Valo [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=871s23cqfo.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=akolli@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=john@phrozen.org \
--cc=seckelmann@datto.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox