From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-bw0-f209.google.com ([209.85.218.209]:43514 "EHLO mail-bw0-f209.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752674Ab0DIGyM convert rfc822-to-8bit (ORCPT ); Fri, 9 Apr 2010 02:54:12 -0400 Received: by bwz1 with SMTP id 1so2295192bwz.21 for ; Thu, 08 Apr 2010 23:54:10 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1270763437-29526-1-git-send-email-gwingerde@gmail.com> <1270763437-29526-5-git-send-email-gwingerde@gmail.com> <201004090032.53842.IvDoorn@gmail.com> Date: Fri, 9 Apr 2010 08:54:08 +0200 Message-ID: Subject: Re: [PATCH 4/9] rt2x00: Remove rt2800 version constants. From: Ivo Van Doorn To: Julian Calaby Cc: Gertjan van Wingerde , "John W. Linville" , linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Apr 9, 2010 at 1:53 AM, Julian Calaby wrote: > On Fri, Apr 9, 2010 at 08:32, Ivo van Doorn wrote: >> On Thursday 08 April 2010, Gertjan van Wingerde wrote: >>> The rt2800 version constants are inconsistent, and the version number don't >>> mean a lot of things anyway. Use the literal values in the code instead of >>> some sort of fabricated version name macro. >>> >>> Signed-off-by: Gertjan van Wingerde >> >> Perhaps a more elegant way of using and defining needs to be found. >> But at least the defined show what the purpose for the values is >> rather then having magical values spread around the code. > > Maybe something like: > > #define RTDEV_IS_RT2883_R1(dev) (rt2x00_rt(dev, RT2883) && \ >                                                   rt2x00_rev(dev) < 0x0300) I considered this as well, but we have many checks which either do rt2x00_rev() < 0xffff but also rt2x00_ref() == 0xffff Ivo