From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Yanbo Li <yanbol@qti.qualcomm.com>
Cc: senthilb@qti.qualcomm.com, dreamfly281@gmail.com,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v3] Add the target register read/write and memory dump debugfs interface
Date: Fri, 24 Oct 2014 16:57:01 +0300 [thread overview]
Message-ID: <87lho5muz6.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1413823085-3187-1-git-send-email-yanbol@qti.qualcomm.com> (Yanbo Li's message of "Tue, 21 Oct 2014 00:38:05 +0800")
Yanbo Li <yanbol@qti.qualcomm.com> writes:
> The debugfs interface reg_addr®_val used to read and write the target
> register.
> The interface mem_addr&mem_val used to dump the targer memory and also
> can be used to assign value to target memory
I think you got the mail from kbuild bot already, but this patch has a
sparse warning:
>> drivers/net/wireless/ath/ath10k/debug.c:1182:26: sparse: incorrect type in assignment (different base types)
drivers/net/wireless/ath/ath10k/debug.c:1182:26: expected restricted __le32 [usertype] <noident>
drivers/net/wireless/ath/ath10k/debug.c:1182:26: got unsigned int [unsigned] [addressable] [usertype] mem_val
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-10-24 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 16:38 [PATCH v3] Add the target register read/write and memory dump debugfs interface Yanbo Li
2014-10-21 6:56 ` Michal Kazior
2014-10-24 13:57 ` Kalle Valo [this message]
2014-10-24 14:22 ` YanBo
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=87lho5muz6.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=dreamfly281@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=senthilb@qti.qualcomm.com \
--cc=yanbol@qti.qualcomm.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