All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: yfw <fengwei.yin@linaro.org>
Cc: andy.green@linaro.org, linux-wireless@vger.kernel.org,
	wcn36xx@lists.infradead.org, k.eugene.e@gmail.com,
	bjorn.andersson@sonymobile.com
Subject: Re: [PATCH 4/5] wcn3620: use new response format for wcn3620 trigger_ba
Date: Thu, 19 Nov 2015 12:41:07 -0500	[thread overview]
Message-ID: <20151119174107.GB12931@localhost> (raw)
In-Reply-To: <564D3FEE.1000208@linaro.org>

On Thu, Nov 19, 2015 at 11:20:14AM +0800, yfw wrote:
> Hi Bob,
> 
> On 2015年11月10日 22:13, Bob Copeland wrote:
> >On Tue, Nov 10, 2015 at 03:08:53PM +0800, fengwei.yin wrote:
> >>Even on 3620, not all cmds switch to wcn36xx_smd_rsp_status_check_v2.
> >>And I don't think wcn36xx_smd_rsp_status_check_v2 should bind to 3620 (it
> >>may be related with firmware).
> >>
> >>In patch v2, the wcn36xx_smd_rsp_status_check_v2 is not bind to 3620. If
> >>you could test on none-3620 platform (I don't have none-3620 plafrom), that
> >>will be great.
> >
> >Sure, I'll take a look today or tomorrow on my hardware.
> >
> 
> Ping...

Oops, sorry.  I can confirm my hardware uses this format.

Turns out, in my backports snapshot I was already carrying a patch for it:

https://github.com/KrasnikovEugene/wcn36xx/commit/7d41270b8c3eee0f72713b4553ca047807c0a00e

-- 
Bob Copeland %% http://bobcopeland.com/

  reply	other threads:[~2015-11-19 17:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 10:02 [PATCH 0/5] wcn36xx: add some new firmware functionalities support Yin, Fengwei
2015-11-09 10:02 ` [PATCH 1/5] wcn36xx: introduce WCN36XX_HAL_AVOID_FREQ_RANGE_IND Yin, Fengwei
2015-11-09 15:37   ` Bob Copeland
2015-11-09 10:02 ` [PATCH 2/5] wcn36xx: swallow two wcn3620 IND messages Yin, Fengwei
2015-11-09 15:38   ` Bob Copeland
2015-11-09 10:02 ` [PATCH 3/5] wcn36xx: handle new hal response format Yin, Fengwei
2015-11-09  9:25   ` kbuild test robot
2015-11-09  9:29   ` fengwei.yin
2015-11-09 10:22   ` kbuild test robot
2015-11-09 15:43   ` Bob Copeland
2015-11-09 10:02 ` [PATCH 4/5] wcn3620: use new response format for wcn3620 trigger_ba Yin, Fengwei
2015-11-09 15:40   ` Bob Copeland
2015-11-10  7:08     ` fengwei.yin
2015-11-10 14:13       ` Bob Copeland
2015-11-11  0:37         ` fengwei.yin
2015-11-19  3:20         ` yfw
2015-11-19 17:41           ` Bob Copeland [this message]
2015-11-20  1:40             ` fengwei.yin
2015-11-20  1:52               ` Bob Copeland
2015-11-20  2:11                 ` fengwei.yin
2015-11-12  4:50     ` Bjorn Andersson
2015-11-12  6:37       ` fengwei.yin
2015-11-22 20:13         ` Eugene Krasnikov
2015-11-09 10:02 ` [PATCH 5/5] wcn3620: use new response format for wcn3620 remove_bsskey Yin, Fengwei

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=20151119174107.GB12931@localhost \
    --to=me@bobcopeland.com \
    --cc=andy.green@linaro.org \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=fengwei.yin@linaro.org \
    --cc=k.eugene.e@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wcn36xx@lists.infradead.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.