From: Bhagavathi Perumal S <bperumal@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH 0/3] ath11k: Add some bug fixes and enhancements in htt stats
Date: Wed, 24 Apr 2019 00:08:30 +0530 [thread overview]
Message-ID: <9d4776387a3b319caf2ff48d6a1a46fc@codeaurora.org> (raw)
In-Reply-To: <875zr4zuaj.fsf@kamboji.qca.qualcomm.com>
On 2019-04-23 19:40, Kalle Valo wrote:
> Bhagavathi Perumal S <bperumal@codeaurora.org> writes:
>
>> This fixes few coding bugs, And adds htt peer stats
>> as a separate debugfs entry and htt stats reset.
>>
>> Bhagavathi Perumal S (3):
>> ath11k: Fix few coding bugs in htt stats
>> ath11k: Add htt peer stats support
>> ath11k: Add debugfs entry to support htt stats reset
>
> Does not compile on x86_64 with GCC 8.1.0:
>
> drivers/net/wireless/ath/ath11k/debugfs_sta.c:432:10: error:
> initialization of 'int (*)(struct inode *, struct file *)' from
> incompatible pointer type 'ssize_t (*)(struct inode *, struct file *)'
> {aka 'long int (*)(struct inode *, struct file *)'}
> [-Werror=incompatible-pointer-types]
Fixed and sent v2 patch.
Thanks,
Bhagavathi.
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-04-23 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 15:52 [PATCH 0/3] ath11k: Add some bug fixes and enhancements in htt stats Bhagavathi Perumal S
2019-04-15 15:52 ` [PATCH 1/3] ath11k: Fix few coding bugs " Bhagavathi Perumal S
2019-04-15 15:52 ` [PATCH 2/3] ath11k: Add htt peer stats support Bhagavathi Perumal S
2019-04-15 15:52 ` [PATCH 3/3] ath11k: Add debugfs entry to support htt stats reset Bhagavathi Perumal S
2019-04-23 14:10 ` [PATCH 0/3] ath11k: Add some bug fixes and enhancements in htt stats Kalle Valo
2019-04-23 18:38 ` Bhagavathi Perumal S [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=9d4776387a3b319caf2ff48d6a1a46fc@codeaurora.org \
--to=bperumal@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@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.