netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211-next 2016-06-09
Date: Fri, 10 Jun 2016 23:16:04 -0700 (PDT)	[thread overview]
Message-ID: <20160610.231604.604019579709781335.davem@davemloft.net> (raw)
In-Reply-To: <1465477466-23756-1-git-send-email-johannes@sipsolutions.net>

From: Johannes Berg <johannes@sipsolutions.net>
Date: Thu,  9 Jun 2016 15:04:25 +0200

> Here's my first set of changes for -next. The only exciting part are the
> changes from Michał to integrate FQ/codel into mac80211's software queues
> to improve cross-station latency and finally solve much of the latency
> issues so many people have spent so much time talking about, but never
> actually working on fixing until he did :)
> 
> Can I ask you to pull net into net-next, preferably before merging this?
> I have a patch that is unsafe without a fix that I submitted through
> mac80211 previously (last time, not the pull request a few minutes ago),
> and I'd prefer not to have that in our -next trees without the fix. If
> you merge net into net-next before this pull request I can fast-forward
> mac80211-next to this merge later.
> 
> Let me know if there's any problem.

Looks good, pulled, thanks!

  reply	other threads:[~2016-06-11  6:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 13:04 pull-request: mac80211-next 2016-06-09 Johannes Berg
2016-06-11  6:16 ` David Miller [this message]
2016-06-11  7:58   ` Johannes Berg
2016-06-11 17:33     ` David Miller

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=20160610.231604.604019579709781335.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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).