All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Peter Oh <poh@codeaurora.org>, Peter Oh <poh@qca.qualcomm.com>,
	ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath: use PRI value given by spec for fixed PRI
Date: Fri, 04 Sep 2015 12:55:55 +0200	[thread overview]
Message-ID: <55E978BB.1030009@neratec.com> (raw)
In-Reply-To: <55E88BA4.7010009@codeaurora.org>

On 09/03/2015 08:04 PM, Peter Oh wrote:
> Hi Zefir,
> 
> I believe the patch below is good to be checked in since you've already made
> change in DFS.
> Can you confirm it?
> 
> [...]
> 
Hi Peter,

yes, after adding the chirp detecting feature to ath9k, I did an internal
certification run with all your patches applied. All good for ETSI (FCC testing
ongoing), so full ACK for the changes.


Cheers,
Zefir



WARNING: multiple messages have this Message-ID (diff)
From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Peter Oh <poh@codeaurora.org>, Peter Oh <poh@qca.qualcomm.com>,
	ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath: use PRI value given by spec for fixed PRI
Date: Fri, 04 Sep 2015 12:55:55 +0200	[thread overview]
Message-ID: <55E978BB.1030009@neratec.com> (raw)
In-Reply-To: <55E88BA4.7010009@codeaurora.org>

On 09/03/2015 08:04 PM, Peter Oh wrote:
> Hi Zefir,
> 
> I believe the patch below is good to be checked in since you've already made
> change in DFS.
> Can you confirm it?
> 
> [...]
> 
Hi Peter,

yes, after adding the chirp detecting feature to ath9k, I did an internal
certification run with all your patches applied. All good for ETSI (FCC testing
ongoing), so full ACK for the changes.


Cheers,
Zefir



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

  reply	other threads:[~2015-09-04 10:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 16:59 [PATCH] ath: use PRI value given by spec for fixed PRI Peter Oh
2015-03-27 16:59 ` Peter Oh
2015-03-30  9:55 ` Zefir Kurtisi
2015-03-30  9:55   ` Zefir Kurtisi
2015-03-30 17:57   ` Peter Oh
2015-03-30 17:57     ` Peter Oh
2015-04-01 10:04     ` Zefir Kurtisi
2015-04-01 10:04       ` Zefir Kurtisi
2015-04-01 21:00       ` Peter Oh
2015-04-01 21:00         ` Peter Oh
2015-04-15 12:41         ` Kalle Valo
2015-04-15 12:41           ` Kalle Valo
2015-04-15 17:10           ` Peter Oh
2015-04-15 17:10             ` Peter Oh
2015-09-03 18:04       ` Peter Oh
2015-09-03 18:04         ` Peter Oh
2015-09-04 10:55         ` Zefir Kurtisi [this message]
2015-09-04 10:55           ` Zefir Kurtisi
2015-09-04 12:55           ` Kalle Valo
2015-09-04 12:55             ` 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=55E978BB.1030009@neratec.com \
    --to=zefir.kurtisi@neratec.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=poh@codeaurora.org \
    --cc=poh@qca.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 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.