ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: ath11k@lists.infradead.org,
	Shashidhar Lakkavalli <slakkavalli@datto.com>
Subject: Re: [PATCH 1/2] ath11k: ignore event 0x6017
Date: Fri,  9 Aug 2019 06:56:34 +0000 (UTC)	[thread overview]
Message-ID: <20190809065634.5E5F860795@smtp.codeaurora.org> (raw)
In-Reply-To: <20190718054910.362-1-john@phrozen.org>

John Crispin <john@phrozen.org> wrote:

> Everytime a new peer gets associated, we see the following message in the log
> - ath11k c000000.wifi1: Unknown eventid: 0x6017
> Ignore this event for now. We probably need to handle the event properly when
> we add OMI support.
> 
> Signed-off-by: Shashidhar Lakkavalli <slakkavalli@datto.com>
> Signed-off-by: John Crispin <john@phrozen.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

2 patches applied to ath11k-post-bringup branch of ath.git, thanks.

e56e2919db5f ath11k: ignore event 0x6017
53738c3c22bc ath11k: convert message from info to dbg

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

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


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

      parent reply	other threads:[~2019-08-09  6:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18  5:49 [PATCH 1/2] ath11k: ignore event 0x6017 John Crispin
2019-07-18  5:49 ` [PATCH 2/2] ath11k: convert message from info to dbg John Crispin
2019-07-18 11:40 ` [PATCH 1/2] ath11k: ignore event 0x6017 Kalle Valo
2019-07-31 14:55   ` Kalle Valo
2019-08-09  6:56 ` Kalle Valo [this message]

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=20190809065634.5E5F860795@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=john@phrozen.org \
    --cc=slakkavalli@datto.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