Return-Path: Subject: Re: ath3k for 2.6.33-rc6 From: Marcel Holtmann To: "Luis R. Rodriguez" Cc: "Luis R. Rodriguez" , linux-bluetooth , lrodriguez@atheros.com In-Reply-To: <20100128215828.GE8069@bombadil.infradead.org> References: <43e72e891001221652s1ead6966r808c72d5b4bdf340@mail.gmail.com> <20100128215828.GE8069@bombadil.infradead.org> Content-Type: text/plain; charset="UTF-8" Date: Wed, 03 Feb 2010 07:35:03 -0800 Message-ID: <1265211303.31341.123.camel@localhost.localdomain> Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Luis, > > sorry about the confusion the other day about overstepping you for a > > push for ath3k into 2.6.33, I'd like to clarify that was not my > > intention, I made the incorrect assumption you received my ping but > > didn't care to push it. I wanted to see what you think its OK to push > > ath3k into the next cycle for the 2.6.33-rc6 release. > > > > Thanks, > > Marcel, was wondering if you have given this some thought. Thanks, that driver ended up in Linus' tree now. So just for future reference for everybody. After -rc2, I only wanna have fixes. There should be no reason why a driver couldn't be ready in time before the merge window. And approx 2-3 weeks grace period after it for new drivers seems to be more than enough to get them cleaned and merged. Regards Marcel