linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: Daniel Halperin <dhalperi@cs.washington.edu>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] iwlwifi: setup agg queues with correct aggregation parameters
Date: Tue, 15 Mar 2011 19:32:56 +0100	[thread overview]
Message-ID: <1300213976.4139.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1300212876.5082.221.camel@wwguy-huron>

On Tue, 2011-03-15 at 11:14 -0700, Guy, Wey-Yi wrote:

> I will prefer let us testing the patch first before push upstream.

I'll send you the patches in a minute.

johannes



  reply	other threads:[~2011-03-15 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 18:25 [PATCH 2/2] iwlwifi: setup agg queues with correct aggregation parameters Daniel Halperin
2011-03-15 18:14 ` Guy, Wey-Yi
2011-03-15 18:32   ` Johannes Berg [this message]
2011-03-15 18:41     ` Daniel Halperin
2011-03-15 18:29 ` Johannes Berg

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=1300213976.4139.4.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=dhalperi@cs.washington.edu \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wey-yi.w.guy@intel.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).