All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Wen Gong <wgong@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4 1/2] ath10k: add bus type for each layout of coredump
Date: Wed, 19 Aug 2020 17:36:49 +0000 (UTC)	[thread overview]
Message-ID: <20200819173649.D7F3FC433CB@smtp.codeaurora.org> (raw)
In-Reply-To: <1569310030-834-2-git-send-email-wgong@codeaurora.org>

Wen Gong <wgong@codeaurora.org> wrote:

> For some hw version, it has more than one bus type, it need to add bus
> type to distinguish different chip.
> 
> Tested-on: QCA6174 SDIO WLAN.RMH.4.4.1-00018-QCARMSWP-1
> 
> Signed-off-by: Wen Gong <wgong@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

2 patches applied to ath-next branch of ath.git, thanks.

c796d513c6ae ath10k: add bus type for each layout of coredump
3c45f21af84e ath10k: sdio: add firmware coredump support

-- 
https://patchwork.kernel.org/patch/11158043/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2020-08-19 17:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24  7:27 [PATCH v4 0/2] add fw coredump for sdio when firmware assert Wen Gong
2019-09-24  7:27 ` Wen Gong
2019-09-24  7:27 ` [PATCH v4 1/2] ath10k: add bus type for each layout of coredump Wen Gong
2019-09-24  7:27   ` Wen Gong
2020-08-19 17:36   ` Kalle Valo [this message]
2020-08-19 17:36   ` Kalle Valo
2019-09-24  7:27 ` [PATCH v4 2/2] ath10k: add fw coredump for sdio when firmware assert Wen Gong
2019-09-24  7:27   ` Wen Gong
2020-08-14 16:36   ` Kalle Valo
2020-08-14 16:36     ` Kalle Valo
2020-08-18  9:23     ` Wen Gong
2020-08-18  9:23       ` Wen Gong
2020-08-19 16:00       ` Kalle Valo
2020-08-19 16:00         ` 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=20200819173649.D7F3FC433CB@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wgong@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.