ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anilkumar Kolli <akolli@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: move per peer pktlog entry to per sta debugfs
Date: Wed, 24 Apr 2019 13:08:28 +0530	[thread overview]
Message-ID: <3753b87a425d38b5c50c33cb4c030451@codeaurora.org> (raw)
In-Reply-To: <871s1szu4f.fsf@kamboji.qca.qualcomm.com>

Hi Kalle,

Thanks for the review.

>> 
>> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org>
> 
> Does not compile:
> 
> drivers/net/wireless/ath/ath11k/debugfs_sta.c:455:11: error:
> initialization of 'ssize_t (*)(struct file *, const char *, size_t,
> loff_t *)' {aka 'long int (*)(struct file *, const char *, long
> unsigned int,  long long int *)'} from incompatible pointer type
> 'ssize_t (*)(struct file *, char *, size_t,  loff_t *)' {aka 'long int
> (*)(struct file *, char *, long unsigned int,  long long int *)'}
> [-Werror=incompatible-pointer-types]
>   .write = ath11k_dbg_sta_write_peer_pktlog,
>            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I am using "arch/x86/configs/x86_64_defconfig" and ath11k enabled, could 
not reproduce this issue.
Kindly share the build instructions.

Thanks
Anil.

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

  reply	other threads:[~2019-04-24  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16  4:41 [PATCH] ath11k: move per peer pktlog entry to per sta debugfs Anilkumar Kolli
2019-04-23 14:14 ` Kalle Valo
2019-04-24  7:38   ` Anilkumar Kolli [this message]
2019-04-24  9:04     ` Anilkumar Kolli
2019-04-24  9:48       ` Sven Eckelmann
2019-05-02 14:53         ` 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=3753b87a425d38b5c50c33cb4c030451@codeaurora.org \
    --to=akolli@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox