Received: by 10.192.165.148 with SMTP id m20csp148219imm; Wed, 9 May 2018 10:12:06 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpawpnRqTs8PxixVezco49xBFYdStblw2LL9W5v1UXQf1Ds35/2vtnBK+wYyCUSU7vIwmMc X-Received: by 2002:a65:6182:: with SMTP id c2-v6mr2272152pgv.219.1525885926752; Wed, 09 May 2018 10:12:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525885926; cv=none; d=google.com; s=arc-20160816; b=ntIOWS1jfs5fCwklYn2r1dT1OKtkw0KX1Q10eVERc5onpUkKUIk3XRxOenJIrMHqcF oHn2gj4b0UjGrlfP6umg53AYS2vCR5jwIZt5LgWuX9C/8ve48wgttwljgO+OQcx/A/Hg 04AUP+lYkyEnPPhUUDYuGIcsCvYDDH7jATTPnD3iDnJpHLrQX2VIbRIVFPQRjAPzQ0T3 ew0YvBYpekfuu1l3JQONFKt01GWPkM9+GrD5sZnCXmjyUZtpAEMyC0Slz1UfpM4XLJsF jrqzPDO07JGGonvInmoeXJlRsHIFsNRXkSS2XpelrBLIcI/iLGX14fc2CEf826vI0mDk BMGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=FKbsZmFq+3e51G/wLSvzGvT30hSShtVeE5BRsB4FOEY=; b=f+LY9DPisl3g7sgc+jZzjgZL0Z5HS7fNq1keW6DhCD5ghw8qQNGT/VBc3leB/tVll9 i9Z8d+F22E/lgn52Yvc5aQzDqfFL0VAOhwBc9eZb5UcDw9ZMYpodZPZywR/ETZ0q1PRT DoPYuuxaRabkClXTYHapQ+e4klWy5eSVDrCsyhGHv/STEVv3NFq24SLbokUHKo91JUar 0UO2Aec3j3ECBEF13NbTfWkS5T9dwgrnFyJIF+Q1dM+63feYjWBXKo2Lv1C1hDnPPP+V pJmHiMckVs1/17fMtSr9ejJ6zejWi+ZYod0kHsPoDWfxaMMstfs4puOO4KqU6rXkbsXQ zSiQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z16-v6si15789039plo.5.2018.05.09.10.11.50; Wed, 09 May 2018 10:12:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965683AbeEIRLl (ORCPT + 99 others); Wed, 9 May 2018 13:11:41 -0400 Received: from ms.lwn.net ([45.79.88.28]:42714 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934980AbeEIRLk (ORCPT ); Wed, 9 May 2018 13:11:40 -0400 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id A5A5A2D0; Wed, 9 May 2018 17:11:39 +0000 (UTC) Date: Wed, 9 May 2018 11:11:36 -0600 From: Jonathan Corbet To: Andrea Parri Cc: Stephen Rothwell , Andrew Morton , Linux-Next Mailing List , Linux Kernel Mailing List , Laurent Dufour , mingo@kernel.org Subject: Re: linux-next: manual merge of the akpm-current tree with the jc_docs tree Message-ID: <20180509111136.127756a8@lwn.net> In-Reply-To: <20180509165249.GA16976@andrea> References: <20180509202508.15c3435a@canb.auug.org.au> <20180509132824.GA14503@andrea> <20180509085920.5fbb32f5@lwn.net> <20180509165249.GA16976@andrea> Organization: LWN.net X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 9 May 2018 18:53:28 +0200 Andrea Parri wrote: > > Now that I look a little closer, I think the real issue is that the > > "features" documentation assumes that there's a Kconfig option for each, > > but there isn't in this case. The lack of a Kconfig option does not, > > this time around, imply that the feature has gone away. > > > > I think that I should probably revert this patch in the short term. > > Longer-term, it would be good to have an alternative syntax for "variable > > set in the arch headers" to describe situations like this. > > Both matters were discussed during v1: > > http://lkml.kernel.org/r/1522774551-9503-1-git-send-email-andrea.parri@amarulasolutions.com > > ... (and the glory details are documented in features-refresh.sh ;-) ). So I'll admit to being confused, since I don't see discussion of the actual topic at hand. > As I suggested above, simply reverting this patch will leave this file, > (and only this file!) out-of-date (and won't resolve the conflict with > Laurent's patch ...). Reverting this patch retains the updates from earlier in the series, and does indeed make the conflict go away, so I'm still confused. What am I missing? Thanks, jon