From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752254AbbAGKmF (ORCPT ); Wed, 7 Jan 2015 05:42:05 -0500 Received: from s3.sipsolutions.net ([5.9.151.49]:35619 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750985AbbAGKmD (ORCPT ); Wed, 7 Jan 2015 05:42:03 -0500 Message-ID: <1420627315.3407.2.camel@sipsolutions.net> Subject: Re: [PATCH] wireless extensions should default to Y From: Johannes Berg To: Pavel Machek Cc: jikos@suse.cz, kernel list , Linus Torvalds , davem@davemloft.net, linux-wireless@vger.kernel.org, netdev@vger.kernel.org Date: Wed, 07 Jan 2015 11:41:55 +0100 In-Reply-To: <20150107101903.GA6563@amd> References: <20150107101903.GA6563@amd> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.7-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2015-01-07 at 11:19 +0100, Pavel Machek wrote: > Do we need following patch on top of > 24a0aa212ee2dbe44360288684478d76a8e20a0a revert? > > I updated kernel today, and (probably because extensions were not > selectable before), the default choice was "N", which is wrong: > oldconfig should result in compatible choices being made, for example > to help bisect. I don't believe we need this. It has been defaulting to N for a long time, it's just that it got thrown out of your config due to building inbetween the patch and its revert. Had you built only before and after that wouldn't be an issue. If we default to Y now we send the wrong signal. If you really need to bisect something wext related you have far bigger issues I'd think, the code hasn't changed *forever*. johannes