From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from fg-out-1718.google.com ([72.14.220.152]:14693 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751446AbYAPQhU (ORCPT ); Wed, 16 Jan 2008 11:37:20 -0500 Received: by fg-out-1718.google.com with SMTP id e21so333875fga.17 for ; Wed, 16 Jan 2008 08:37:18 -0800 (PST) To: Johannes Berg Subject: Re: [RFC] mac80211: proper short-slot handling Date: Wed, 16 Jan 2008 17:37:00 +0100 Cc: linux-wireless , Ron Rindjunsky , Michael Buesch , Michael Wu , "Luis R. Rodriguez" , bruno randolf , Nick Kossifidis , Yanbo Li , Tomas Winkler , Stefano Brivio , Zhu Yi , Reinette Chatre , Daniel Drake References: <1199974496.3861.80.camel@johannes.berg> <200801102000.44722.IvDoorn@gmail.com> <1200490221.5887.170.camel@johannes.berg> In-Reply-To: <1200490221.5887.170.camel@johannes.berg> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Message-Id: <200801161737.00682.IvDoorn@gmail.com> (sfid-20080116_163724_317095_0BE13226) From: Ivo van Doorn Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wednesday 16 January 2008, Johannes Berg wrote: > Ivo, > > > > If you think it is the right approach, maybe try converting your driver > > > and see if that results in any problems, if not, send me the patch and > > > I'll integrate it. > > > > The convertion was very easy, and like I said cleaned up some hacks. :) > > Thanks. What is this diffed on? I tried importing it into my current > patch but it failed, do I have to wait for John to pull in your recent > pull request? John already merged the 2.0.14 release into the everything branch, so no need to wait on that. The remaining patches which have been send but not yet merged are bugfixes which won't cause a collision with the short-slot patch. Not sure where I diffed it against, I probably have to rebase it anyway since I currently have a few major patches pending for the 2.1.0 release which will drastically change the entire interface handling in rt2x00. When do you plan to send the patch for inclusion? I can rebase the patch and make it part of the 2.1.0 release of this weekend or release 2.1.0 and rebase the patch against that. Ivo