linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, Michael Wu <flamingice@sourmilk.net>
Subject: Re: [TAKE 2][PATCH 0/3] IEEE802.11e/WMM TS management and DLS  support
Date: Fri, 01 Jun 2007 09:01:39 +0800	[thread overview]
Message-ID: <1180659699.3109.101.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20070531180445.GB3706@tuxdriver.com>

On Thu, 2007-05-31 at 14:04 -0400, John W. Linville wrote:
> Please also submit a patch series that applies against
> linux-2.6.22-rc3 (or later) and adds whatever else might be needed
> that is missing there.  This one changes code that is currently only
> in wireless-dev. 

Thanks! Will do.

-yi

      parent reply	other threads:[~2007-06-01  1:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 11:52 [TAKE 2][PATCH 0/3] IEEE802.11e/WMM TS management and DLS support Zhu Yi
2007-05-31 18:04 ` John W. Linville
2007-05-31 19:55   ` Michael Wu
2007-06-01  1:04     ` Zhu Yi
2007-06-11 19:05       ` John W. Linville
2007-06-01  1:01   ` Zhu Yi [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=1180659699.3109.101.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=flamingice@sourmilk.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).