From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: akolli@codeaurora.org, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] ath10k: pci: Only dump ATH10K_MEM_REGION_TYPE_IOREG when safe
Date: Thu, 19 Dec 2019 14:29:40 +0000 [thread overview]
Message-ID: <4a8b7913-c9b9-dd67-124d-b4f71747c849@linaro.org> (raw)
In-Reply-To: <87sglg5rb0.fsf@kamboji.qca.qualcomm.com>
On 19/12/2019 14:21, Kalle Valo wrote:
> 'dmesg | grep ath10k' should show it.
[ 6.579772] ath10k_pci 0000:01:00.0: firmware ver 10.4-3.9.0.2-00044
api 5 features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32
c3e1b393
WARNING: multiple messages have this Message-ID (diff)
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: akolli@codeaurora.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org
Subject: Re: [PATCH 1/2] ath10k: pci: Only dump ATH10K_MEM_REGION_TYPE_IOREG when safe
Date: Thu, 19 Dec 2019 14:29:40 +0000 [thread overview]
Message-ID: <4a8b7913-c9b9-dd67-124d-b4f71747c849@linaro.org> (raw)
In-Reply-To: <87sglg5rb0.fsf@kamboji.qca.qualcomm.com>
On 19/12/2019 14:21, Kalle Valo wrote:
> 'dmesg | grep ath10k' should show it.
[ 6.579772] ath10k_pci 0000:01:00.0: firmware ver 10.4-3.9.0.2-00044
api 5 features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32
c3e1b393
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-12-19 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 13:15 [PATCH 0/2] ath10k: pci: Two PCI related fixups Bryan O'Donoghue
2019-12-19 13:15 ` Bryan O'Donoghue
2019-12-19 13:15 ` [PATCH 1/2] ath10k: pci: Only dump ATH10K_MEM_REGION_TYPE_IOREG when safe Bryan O'Donoghue
2019-12-19 13:15 ` Bryan O'Donoghue
2019-12-19 13:53 ` Kalle Valo
2019-12-19 13:53 ` Kalle Valo
2019-12-19 14:15 ` Bryan O'Donoghue
2019-12-19 14:15 ` Bryan O'Donoghue
2019-12-19 14:21 ` Kalle Valo
2019-12-19 14:21 ` Kalle Valo
2019-12-19 14:29 ` Bryan O'Donoghue [this message]
2019-12-19 14:29 ` Bryan O'Donoghue
2020-01-26 10:23 ` Kalle Valo
2020-01-26 10:23 ` Kalle Valo
2019-12-19 13:15 ` [PATCH 2/2] ath10k: pci: Fix comment on ath10k_pci_dump_memory_sram Bryan O'Donoghue
2019-12-19 13:15 ` Bryan O'Donoghue
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=4a8b7913-c9b9-dd67-124d-b4f71747c849@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=akolli@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.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.