From: "John W. Linville" <linville@tuxdriver.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: yi.zhu@intel.com, linux-wireless@vger.kernel.org,
Michael Wu <flamingice@sourmilk.net>
Subject: Re: IEEE802.11e/WMM TS management and DLS support
Date: Tue, 12 Jun 2007 10:02:17 -0400 [thread overview]
Message-ID: <20070612140217.GC310@tuxdriver.com> (raw)
In-Reply-To: <20070607224315.6dadffca@griffin.suse.cz>
On Thu, Jun 07, 2007 at 10:43:15PM +0200, Jiri Benc wrote:
> On Wed, 6 Jun 2007 16:21:54 +0800, Zhu Yi wrote:
> > This is a patch series for IEEE802.11e/WMM support against
> > linux-2.6.22-rc4.
> >
> > [PATCH 1/3] mac80211: add IEEE802.11e/WMM structures
> > [PATCH 2/3] mac80211: IEEE802.11e/WMM TS management and DLS support
> > [PATCH 3/3] mac80211: debugfs support for TSM and DLS
> I see you already applied those patches. I haven't had a time to look
> at the second patch in this resent version yet, but even from the first
> and third one it's clear they still need a lot of work (for example,
> adding cfg80211 support instead of that debugfs interface isn't going
> to be a few lines long patch).
>
> Please revert them.
I think you will agree that Yi has been making a good effort to correct
problems identified with this patch series. I think it is best to
continue integrating those patches into the wireless-dev tree for now.
Once the code is agreeable to those concerned (including a reasonable
API for DLS establishment), then we can ask for Yi (or someone else)
to submit a clean patchset for sending upstream. As long as the
individual patches are focused on a particular feature, git provides
facilities for combining patches that are fairly robust and easy
to manage. So, creating a clean patchset should be no great hardship.
John
P.S. The future of wireless-dev is still open for dicussion. I think
it can still be useful for integrating "in progress" patches and
feeding them to -mm for early testing. However, I definitely would
like to reduce the delta between wireless-dev and wireless-2.6 as
much as possible and as soon as possible.
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2007-06-12 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 8:21 IEEE802.11e/WMM TS management and DLS support Zhu Yi
2007-06-06 20:00 ` Johannes Berg
2007-06-08 8:16 ` Zhu Yi
2007-06-08 9:30 ` Johannes Berg
2007-06-08 13:35 ` Cohen, Guy
2007-06-07 20:43 ` Jiri Benc
2007-06-08 3:52 ` jketreno
2007-06-07 21:12 ` Michael Wu
2007-06-08 4:41 ` jketreno
2007-06-07 22:40 ` Jiri Benc
2007-06-08 1:53 ` Zhu Yi
2007-06-07 22:40 ` Michael Wu
2007-06-08 2:42 ` Zhu Yi
2007-06-12 14:02 ` 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=20070612140217.GC310@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=yi.zhu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.