From: "John W. Linville" <linville@tuxdriver.com>
To: Dave Taht <dave.taht@bufferbloat.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] Treat IPv6 diffserv the same as ipv4 diffserv for 802.11e
Date: Wed, 21 Dec 2011 15:09:37 -0500 [thread overview]
Message-ID: <20111221200937.GG11842@tuxdriver.com> (raw)
In-Reply-To: <1324456905-2628-2-git-send-email-dave.taht@bufferbloat.net>
On Wed, Dec 21, 2011 at 12:41:45AM -0800, Dave Taht wrote:
> Wireless will select a different hardware queue based on the
> top 3 bits of the diffserv field, for ipv4. Extend that queue
> selection mechanism to ipv6, and make the calls orthogonal.
The patch itself seems fine to me. But the format needs work:
http://linux.yyz.us/patch-format.html
Would you mind fixing-up the email and resubmitting?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2011-12-21 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 8:41 [PATCH 0/1] Treat IPv6 diffserv the same as ipv4 diffserv for 802.11e Dave Taht
2011-12-21 8:41 ` [PATCH 1/1] " Dave Taht
2011-12-21 20:09 ` John W. Linville [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=20111221200937.GG11842@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dave.taht@bufferbloat.net \
--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).