From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:58013 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753846AbZJIAz6 (ORCPT ); Thu, 8 Oct 2009 20:55:58 -0400 Date: Thu, 08 Oct 2009 17:55:53 -0700 (PDT) Message-Id: <20091008.175553.139810708.davem@davemloft.net> To: mb@bu3sch.de Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: pull request: wireless-2.6 2009-10-08 From: David Miller In-Reply-To: <200910090116.46513.mb@bu3sch.de> References: <20091008223454.GB2798@tuxdriver.com> <200910090108.08838.mb@bu3sch.de> <200910090116.46513.mb@bu3sch.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: From: Michael Buesch Date: Fri, 9 Oct 2009 01:16:44 +0200 > And there's no reason to rush this fix into mainline. I think it's worthwhile because people turn the DMA API debugger on and it's going to spit out warnings that "don't matter" until you guys fix this. I looked at the patch you guys are so up in arms about, and frankly it looks perfectly fine to me. If you want to implement the fix "perfectly", and "to your standards", then fine. But do it in net-next-2.6 as a follow-on patch to this one. I'm not undoing John's pull request just for this. :-)