From: Kalle Valo <kvalo@codeaurora.org>
To: Mao Wenan <maowenan@huawei.com>
Cc: kernel-janitors@vger.kernel.org, milehu@codeaurora.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, ath11k@lists.infradead.org,
julia.lawall@lip6.fr, mpubbise@codeaurora.org,
msinada@codeaurora.org, periyasa@codeaurora.org,
davem@davemloft.net
Subject: Re: [PATCH -next] ath11k: add dependency for struct ath11k member debug
Date: Wed, 15 Jan 2020 09:18:20 +0000 (UTC) [thread overview]
Message-ID: <20200115091820.091F2C433A2@smtp.codeaurora.org> (raw)
In-Reply-To: <20191213012417.130719-1-maowenan@huawei.com>
Mao Wenan <maowenan@huawei.com> wrote:
> If CONFIG_ATH11K, CONFIG_MAC80211_DEBUGFS are set,
> and CONFIG_ATH11K_DEBUGFS is not set, below error can be found,
> drivers/net/wireless/ath/ath11k/debugfs_sta.c: In function ath11k_dbg_sta_open_htt_peer_stats:
> drivers/net/wireless/ath/ath11k/debugfs_sta.c:411:4: error: struct ath11k has no member named debug
> ar->debug.htt_stats.stats_req = stats_req;
>
> It is to add the dependency for the member of struct ath11k.
>
> Fixes: d5c65159f289 ("ath11k: driver for Qualcomm IEEE 802.11ax devices")
> Signed-off-by: Mao Wenan <maowenan@huawei.com>
Arnd already did something what I proposed:
https://patchwork.kernel.org/patch/11321921/
Patch set to Superseded.
--
https://patchwork.kernel.org/patch/11289709/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2020-01-15 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 1:24 [PATCH -next] ath11k: add dependency for struct ath11k member debug Mao Wenan
2019-12-13 1:24 ` Mao Wenan
2019-12-13 1:24 ` Mao Wenan
2019-12-19 13:38 ` Kalle Valo
2019-12-19 13:38 ` Kalle Valo
2019-12-19 13:38 ` Kalle Valo
2020-01-15 9:18 ` Kalle Valo
2020-01-15 9:18 ` Kalle Valo
2020-01-15 9:18 ` 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=20200115091820.091F2C433A2@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maowenan@huawei.com \
--cc=milehu@codeaurora.org \
--cc=mpubbise@codeaurora.org \
--cc=msinada@codeaurora.org \
--cc=netdev@vger.kernel.org \
--cc=periyasa@codeaurora.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.