From: Johannes Berg <johannes@sipsolutions.net>
To: Guy Cohen <guy.cohen@intel.com>
Cc: Ron Rindjunsky <ron.rindjunsky@intel.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
flamingice@sourmilk.net, tomas.winkler@intel.com
Subject: Re: [PATCH 0/15] mac80211/iwlwifi (#everything): integrate IEEE802.11n support
Date: Thu, 15 Nov 2007 17:04:43 +0100 [thread overview]
Message-ID: <1195142683.13846.62.camel@johannes.berg> (raw)
In-Reply-To: <247d6d340711150233h7988220fifb0d34170d16a979@mail.gmail.com> (sfid-20071115_103946_582002_A2DCEB54)
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Guy,
> We understand that these two issues need to be taken care of, and they
> will be. My concern is that if current patches won't be merged soon,
> we will have to pay the effort to rebase the patches again. We are
> very limited with resources dedicated to supporting the merge of
> 802.11n to wireless-dev. This mailing list taught us in the "hard way"
> in the recent months: submit often submit early... So for making Ron's
> work efficient I suggest to merge his patches and let him do the fixes
> on top of them, specially since the two fixes are not 802.11n core
> critical issues and don't break any existing working flows. Do you
> feel comfortable with this approach?
I understand your concern, however, if for some reason this doesn't
happen quickly enough we'll end up with code that is vulnerable in weird
ways. I'd have no issue with these patches if deaggregation support was
optional until we have the patchset that reworks that code. Can we do
that?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2007-11-15 16:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 15:29 [PATCH 0/15] mac80211/iwlwifi (#everything): integrate IEEE802.11n support Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 01/15] mac80211: adding MAC80211_HT config variable Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 02/15] mac80211: adding 802.11n definitions in ieee80211.h Ron Rindjunsky
2007-11-14 16:04 ` Johannes Berg
2007-11-14 16:45 ` Ron Rindzonski
2007-11-15 13:36 ` Johannes Berg
2007-11-15 18:03 ` [PATCH 02/15] mac80211: adding 802.11n definitions inieee80211.h Rindjunsky, Ron
2007-11-14 15:29 ` [PATCH 03/15] mac80211: adding 802.11n HT framework definitions Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 04/15] mac80211: adding 802.11n IEs handling Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 05/15] mac80211: adding 802.11n essential A-MPDU addBA capability Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 06/15] mac80211: adding 802.11n essential A-MSDU Rx capability Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 07/15] mac80211: adding 802.11n configuration flows Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 08/15] iwlwifi: 802.11n remove unnecessary config dependency Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 09/15] iwlwifi: 802.11n new framework structures preperation Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 10/15] iwlwifi: 802.11n configuring hw_mode parameters to support HT in A/G Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 11/15] iwlwifi: 802.11n handling probe request HT IE Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 12/15] iwlwifi: 802.11n comply HT self configuration flow with mac80211 framework Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 13/15] iwlwifi: 802.11n comply HT add station " Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 14/15] iwlwifi: 802.11n comply HT rate scaling flows " Ron Rindjunsky
2007-11-14 15:29 ` [PATCH 15/15] iwlwifi: 802.11n add support to 8K A-MSDU Rx frames Ron Rindjunsky
2007-11-14 16:11 ` [PATCH 0/15] mac80211/iwlwifi (#everything): integrate IEEE802.11n support Johannes Berg
2007-11-15 10:33 ` Guy Cohen
2007-11-15 16:04 ` Johannes Berg [this message]
2007-11-15 18:06 ` Ron Rindzonski
2007-11-15 18:11 ` Johannes Berg
2007-11-15 18:36 ` Ron Rindzonski
2007-11-16 15:59 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2007-11-26 14:14 Ron Rindjunsky
2007-11-27 1:34 ` Luis R. Rodriguez
2007-11-27 9:12 ` Ron Rindjunsky
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=1195142683.13846.62.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=flamingice@sourmilk.net \
--cc=guy.cohen@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ron.rindjunsky@intel.com \
--cc=tomas.winkler@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).