All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Bhagavathi Perumal S <bperumal@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH 0/3] ath11k: Add some bug fixes and enhancements in htt stats
Date: Tue, 23 Apr 2019 17:10:44 +0300	[thread overview]
Message-ID: <875zr4zuaj.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1555343569-2072-1-git-send-email-bperumal@codeaurora.org> (Bhagavathi Perumal S.'s message of "Mon, 15 Apr 2019 21:22:46 +0530")

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]

-- 
Kalle Valo

_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  parent reply	other threads:[~2019-04-23 14:10 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 ` Kalle Valo [this message]
2019-04-23 18:38   ` [PATCH 0/3] ath11k: Add some bug fixes and enhancements in htt stats Bhagavathi Perumal S

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=875zr4zuaj.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=bperumal@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.