ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: gregkh@linuxfoundation.org
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: patch "ath10k: drop probe responses when too many are queued" added to staging-testing
Date: Sat, 7 Nov 2015 10:43:52 +0200	[thread overview]
Message-ID: <87mvuq9p2v.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <14468483293347@kroah.com> (gregkh@linuxfoundation.org's message of "Fri, 6 Nov 2015 14:18:49 -0800")

Hi Greg,

<gregkh@linuxfoundation.org> writes:

> This is a note to let you know that I've just added the patch titled
>
>     ath10k: drop probe responses when too many are queued
>
> to my staging git tree which can be found at
>     git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> in the staging-testing branch.
>
> The patch will show up in the next release of the linux-next tree
> (usually sometime within the next 24 hours during the week.)
>
> The patch will be merged to the staging-next branch sometime soon,
> after it passes testing, and the merge window is open.
>
> If you have any questions about this process, please let me know.

Did you apply this and the few other ath10k patches to staging by
mistake? I had already applied them to my ath.git tree and linus already
has them:

7b7da0a02192 ath10k: drop probe responses when too many are queued

-- 
Kalle Valo

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

       reply	other threads:[~2015-11-07  8:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <14468483293347@kroah.com>
2015-11-07  8:43 ` Kalle Valo [this message]
2015-11-07 17:25   ` patch "ath10k: drop probe responses when too many are queued" added to staging-testing Greg KH

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=87mvuq9p2v.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox