From: Rakesh Pillai <pillair@codeaurora.org>
To: peter.oh@bowerswilkins.com
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: FW: [PATCH v2] ath10k: Report low ack rssi based on the reason code
Date: Thu, 04 Apr 2019 17:41:12 +0530 [thread overview]
Message-ID: <73e869e8f82a3395cfefaf1272d07906@codeaurora.org> (raw)
In-Reply-To: <8c3110f20aec4c4a90bb679c4551b1fc@aphydexm01b.ap.qualcomm.com>
>> diff --git a/drivers/net/wireless/ath/ath10k/wmi.h
>> b/drivers/net/wireless/ath/ath10k/wmi.h
>> index e1c40bb..3ccd79e 100644
>> --- a/drivers/net/wireless/ath/ath10k/wmi.h
>> +++ b/drivers/net/wireless/ath/ath10k/wmi.h
>> @@ -6797,6 +6797,8 @@ struct wmi_vdev_start_ev_arg {
>>
>> struct wmi_peer_kick_ev_arg {
>> const u8 *mac_addr;
>> + u32 reason;
>> + bool reason_code_valid;
>> };
>>
> Adding extra members to this structure breaks structure consistency
> between FW and host driver since FW doesn't have such members.
>
> Peter
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
struct wmi_peer_sta_kickout_event is used for parsing event from non-tlv
firmwares and
struct wmi_tlv_peer_sta_kickout_event is used for parsing event from
tlv firmwares.
Both of the above structures maintain consistency with the respective
FW.
struct wmi_peer_kick_ev_arg is used only for internal ath10k operations
only.
Thanks,
Rakesh Pillai.
next prev parent reply other threads:[~2019-04-04 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 7:23 [PATCH v2] ath10k: Report low ack rssi based on the reason code Rakesh Pillai
2019-04-03 16:58 ` Peter Oh
[not found] ` <8c3110f20aec4c4a90bb679c4551b1fc@aphydexm01b.ap.qualcomm.com>
2019-04-04 12:11 ` Rakesh Pillai [this message]
2019-10-03 13:03 ` Kalle Valo
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=73e869e8f82a3395cfefaf1272d07906@codeaurora.org \
--to=pillair@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=peter.oh@bowerswilkins.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;
as well as URLs for NNTP newsgroup(s).