linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/4] mac80211: wme.c replace QD_NUM macro with static inline
Date: Wed, 09 Jul 2008 13:01:41 -0700	[thread overview]
Message-ID: <1215633701.476.90.camel@brick> (raw)
In-Reply-To: <1215633420.3246.47.camel@johannes.berg>

On Wed, 2008-07-09 at 21:57 +0200, Johannes Berg wrote:
> While I don't really disagree with this patch, let's not do it at least
> for now so we don't break davem's TX MQ rework needlessly.
> 

Sure, I'll keep an eye out for his stuff to go in and resubmit at a
later time.

Harvey


      reply	other threads:[~2008-07-09 20:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 19:44 [PATCH 2/4] mac80211: wme.c replace QD_NUM macro with static inline Harvey Harrison
2008-07-09 19:57 ` Johannes Berg
2008-07-09 20:01   ` Harvey Harrison [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=1215633701.476.90.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).