From: Ben Greear <greearb@candelatech.com>
To: greearb@candelatech.com
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/8] ath10k: scan should handle scan-start-failed event properly.
Date: Mon, 12 Jan 2015 11:53:06 -0800 [thread overview]
Message-ID: <54B42622.5090404@candelatech.com> (raw)
In-Reply-To: <1421090992-14971-1-git-send-email-greearb@candelatech.com>
Sorry about the resends...had mail-server issue, should be resolved now.
Thanks,
Ben
On 01/12/2015 11:29 AM, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> In case firmware fails to start the scan, then complete
> the start condition and clean up so that driver does not
> block on timeout.
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 1/8] ath10k: scan should handle scan-start-failed event properly.
Date: Mon, 12 Jan 2015 11:53:06 -0800 [thread overview]
Message-ID: <54B42622.5090404@candelatech.com> (raw)
In-Reply-To: <1421090992-14971-1-git-send-email-greearb@candelatech.com>
Sorry about the resends...had mail-server issue, should be resolved now.
Thanks,
Ben
On 01/12/2015 11:29 AM, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> In case firmware fails to start the scan, then complete
> the start condition and clean up so that driver does not
> block on timeout.
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-01-12 19:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 19:29 [PATCH 1/8] ath10k: scan should handle scan-start-failed event properly greearb
2015-01-12 19:29 ` greearb
2015-01-12 19:53 ` Ben Greear [this message]
2015-01-12 19:53 ` Ben Greear
2015-01-13 13:42 ` Kalle Valo
2015-01-13 13:42 ` Kalle Valo
2015-01-13 16:15 ` Ben Greear
2015-01-13 16:15 ` Ben Greear
-- strict thread matches above, loose matches on Subject: below --
2015-01-12 19:41 greearb
2015-01-12 19:41 ` greearb
2015-01-12 18:32 greearb
2015-01-12 18:32 ` greearb
2015-02-04 8:37 ` Kalle Valo
2015-02-04 8:37 ` Kalle Valo
2015-02-04 15:31 ` Ben Greear
2015-02-04 15:31 ` Ben Greear
2015-02-15 15:03 ` Kalle Valo
2015-02-15 15:03 ` 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=54B42622.5090404@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.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.