linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: patch "ath10k: drop probe responses when too many are queued" added to staging-testing
Date: Sat, 7 Nov 2015 09:25:32 -0800	[thread overview]
Message-ID: <20151107172532.GA26631@kroah.com> (raw)
In-Reply-To: <87mvuq9p2v.fsf@kamboji.qca.qualcomm.com>

On Sat, Nov 07, 2015 at 10:43:52AM +0200, Kalle Valo wrote:
> 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

Yeah, sorry about that, my script went wrong when I merged in Linus's
latest tree into my branch.  Sorry for the noise.

greg k-h

      reply	other threads:[~2015-11-07 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <14468483293347@kroah.com>
2015-11-07  8:43 ` patch "ath10k: drop probe responses when too many are queued" added to staging-testing Kalle Valo
2015-11-07 17:25   ` Greg KH [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=20151107172532.GA26631@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --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;
as well as URLs for NNTP newsgroup(s).