From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from c60.cesmail.net ([216.154.195.49]:48585 "EHLO c60.cesmail.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753994Ab0DSPx0 (ORCPT ); Mon, 19 Apr 2010 11:53:26 -0400 Subject: Re: [PATCH v3 42/97] ath9k: Make bf_desc of ath_buf opaque From: Pavel Roskin To: Felix Fietkau Cc: "Luis R. Rodriguez" , linville@tuxdriver.com, linux-wireless@vger.kernel.org, Vasanthakumar Thiagarajan In-Reply-To: <4BC8E027.1030807@openwrt.org> References: <1271367582-992-1-git-send-email-lrodriguez@atheros.com> <1271367582-992-43-git-send-email-lrodriguez@atheros.com> <1271455259.16507.43.camel@mj> <4BC8E027.1030807@openwrt.org> Content-Type: text/plain Date: Mon, 19 Apr 2010 11:53:24 -0400 Message-Id: <1271692404.9026.15.camel@mj> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sat, 2010-04-17 at 00:09 +0200, Felix Fietkau wrote: > > The obvious downside is that bf_desc becomes compatible with pointers of > > any type. > Because on AR9300 where it's used, it points to a struct ar9003_txc instead. OK, fair enough. -- Regards, Pavel Roskin