From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:37976 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751755AbaETSY6 (ORCPT ); Tue, 20 May 2014 14:24:58 -0400 Message-ID: <1400610273.4474.6.camel@jlt4.sipsolutions.net> (sfid-20140520_202501_013531_F1DDC756) Subject: Re: [PATCH] wireless-regdb: add DFS CAC time parameter From: Johannes Berg To: "John W. Linville" Cc: Janusz Dziedzic , "Luis R. Rodriguez" , "wireless-regdb@lists.infradead.org" , linux-wireless Date: Tue, 20 May 2014 20:24:33 +0200 In-Reply-To: <20140520180832.GD13981@tuxdriver.com> (sfid-20140520_201518_644762_1B148A19) References: <1399624824-9204-1-git-send-email-janusz.dziedzic@tieto.com> <20140520142453.GB13981@tuxdriver.com> <20140520180832.GD13981@tuxdriver.com> (sfid-20140520_201518_644762_1B148A19) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, 2014-05-20 at 14:08 -0400, John W. Linville wrote: > > I can add support for version 19 and 20 in one crda. I am not sure > > this is the best option. > > BTW what about versions < 19? How do we handle this this days? > > What about older CRDA with newer wireless-regdb? Do we need to worry about that? I think we should, but if we can't then at least can we cut to an extensible format? (and yeah, I know I was part of defining the format ...) johannes