Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753464AbdIGFE5 (ORCPT ); Thu, 7 Sep 2017 01:04:57 -0400 Received: from mga01.intel.com ([192.55.52.88]:58304 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750742AbdIGFEz (ORCPT ); Thu, 7 Sep 2017 01:04:55 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,356,1500966000"; d="scan'208";a="1215772961" From: "Coelho, Luciano" To: "torvalds@linux-foundation.org" CC: "linux-kernel@vger.kernel.org" , linuxwifi , "Berg, Johannes" , "akpm@linux-foundation.org" , "kvalo@codeaurora.org" , "netdev@vger.kernel.org" , "davem@davemloft.net" , "linux-wireless@vger.kernel.org" , "Grumbach, Emmanuel" Subject: Re: [GIT] Networking Thread-Topic: [GIT] Networking Thread-Index: AQHTJ2e1r+p5kKpHi0+CCZ9Rdj3td6KovzaAgAAM6gCAAAH1AA== Date: Thu, 7 Sep 2017 05:04:49 +0000 Message-ID: <1504760688.5400.91.camel@intel.com> References: <20170905.214143.826912481689443792.davem@davemloft.net> <1504757495.5400.89.camel@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.30.157] Content-Type: text/plain; charset="utf-8" Content-ID: <68CC818954C9E64192F6272D7C480C10@intel.com> MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id v87555bo030018 Content-Length: 996 Lines: 29 On Wed, 2017-09-06 at 21:57 -0700, Linus Torvalds wrote: > On Wed, Sep 6, 2017 at 9:11 PM, Coelho, Luciano > wrote: > > > > This seems to be a problem with backwards-compatibility with FW version > > 27. We are now in version 31[1] and upgrading will probably fix that. > > I can confirm that fw version 31 works. Great, so I know for sure that this is a backwards-compatibility issue with the FW API. > > But obviously the driver should not fail miserably like this with > > version 27, because it claims to support it still. > > Not just "claims to support it", but if it's what is shipped with a > fairly recent distro like an up-to-date version of F26, I would really > hope that the driver can still work with it. I totally agree, we support a bunch of older versions for that exact reason. We just don't really test all the supported versions very often. We should probably change that. I'll make sure it still works with version 27. -- Cheers, Luca.