Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1816192ybh; Fri, 13 Mar 2020 07:56:10 -0700 (PDT) X-Google-Smtp-Source: ADFU+vuxZk6Wvx8vSowuKwI4IznDg6d/HvSPEtw/8pDK/2hkmn3JWatiKrM6c4h5tIbac7oGtArT X-Received: by 2002:a9d:b89:: with SMTP id 9mr11588572oth.297.1584111370156; Fri, 13 Mar 2020 07:56:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584111370; cv=none; d=google.com; s=arc-20160816; b=r5vseOZfYaEaUWtGRVBdW3ubAFwBtYNXRSVTQiNN3cXLouSvyv0KpB+tnW8lql/Ew5 9pKlCjIqaM9DM9ahT+lEYpzhgX/IrYgCvDfdDc/t2eHXO8qxvi6TVazTfvPSHccvCytr AGTSQxfo8DQyA1Pd4CwciQu7WeaSYR1lVTsmEosNs9SKeOOQcvTi3voX/PtYq/NIQHV8 A6RmVSOo/3IMkvdxwElobZ3c1R/jMR9G44GGCRq6i8sIQk3KFnx7439incCMrWhf/jvy dbGSeuLRPiy/PBrDGfopu8VgsTIfe/eHaGWvl2aC3i9WxDsqzs3K6GDhcNkp8uuqvpBu y/Sw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :mime-version:references:in-reply-to:date:cc:to:from:subject; bh=rOCed0Eo+1Qjc+f0g71ti5VVbFUa/aAT+Gt9WGz04gs=; b=j8TuqcAzntCWiwoOTp/S/T9h6vcBNeiip/h3fdhiXS37PywMsO8tjSwrj1xIsFVWB4 UHB85tkMPy2gUBGsjtB+4fbO5cc1NOtU2fem0oDVGRaHOq63clcKpdvmwwuAA5NA93UK hzkOtyf32hr8fmiggo4C/URdyXFx6JmSWNRAuoLT5DIkbipF92vCau0jiEocDM++tnnQ nKskhs/If9QkTCfy025XJ/fVEroVzQB5+wLb6w6t6iMKVjNpD9V04inXUpzDVmG21oFw MFmsFFViFdpXo0Yh+OGwUzWN0kXjBzjWO5ciZIEWaNCAawopgIiCXkSQ1bcVc4r1G+xA O2Og== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 67si1260637otj.108.2020.03.13.07.55.56; Fri, 13 Mar 2020 07:56:10 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726692AbgCMOyZ (ORCPT + 99 others); Fri, 13 Mar 2020 10:54:25 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:7806 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726528AbgCMOyZ (ORCPT ); Fri, 13 Mar 2020 10:54:25 -0400 Received: from pps.filterd (m0098410.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 02DEpaEO116494 for ; Fri, 13 Mar 2020 10:54:24 -0400 Received: from e06smtp02.uk.ibm.com (e06smtp02.uk.ibm.com [195.75.94.98]) by mx0a-001b2d01.pphosted.com with ESMTP id 2yr125m2qc-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 13 Mar 2020 10:54:22 -0400 Received: from localhost by e06smtp02.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 13 Mar 2020 14:54:19 -0000 Received: from b06cxnps3074.portsmouth.uk.ibm.com (9.149.109.194) by e06smtp02.uk.ibm.com (192.168.101.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Fri, 13 Mar 2020 14:54:16 -0000 Received: from d06av24.portsmouth.uk.ibm.com (mk.ibm.com [9.149.105.60]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 02DEsFEP53149850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 13 Mar 2020 14:54:15 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0E8964203F; Fri, 13 Mar 2020 14:54:15 +0000 (GMT) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7407542045; Fri, 13 Mar 2020 14:54:13 +0000 (GMT) Received: from localhost.localdomain (unknown [9.85.190.184]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTP; Fri, 13 Mar 2020 14:54:13 +0000 (GMT) Subject: Re: linux-next: manual merge of the akpm-current tree with the integrity tree From: Mimi Zohar To: Stephen Rothwell , Andrew Morton , Mimi Zohar , Dmitry Kasatkin , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra Cc: Linux Next Mailing List , Linux Kernel Mailing List , Andrea Arcangeli , Nayna Jain , Marco Elver , "Paul E. McKenney" Date: Fri, 13 Mar 2020 10:54:12 -0400 In-Reply-To: <20200313210714.58ff3d99@canb.auug.org.au> References: <20200313210714.58ff3d99@canb.auug.org.au> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 20031314-0008-0000-0000-0000035CADF7 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 20031314-0009-0000-0000-00004A7DFB59 Message-Id: <1584111252.5188.16.camel@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138,18.0.572 definitions=2020-03-13_05:2020-03-12,2020-03-13 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 priorityscore=1501 malwarescore=0 bulkscore=0 phishscore=0 mlxlogscore=999 spamscore=0 suspectscore=0 lowpriorityscore=0 mlxscore=0 clxscore=1015 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2003130077 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2020-03-13 at 21:07 +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the akpm-current tree got a conflict in: > > arch/x86/Kconfig > > between commits: > > 9e2b4be377f0 ("ima: add a new CONFIG for loading arch-specific policies") > > from the integrity tree and commit: > > faaa52178603 ("userfaultfd: wp: add WP pagetable tracking to x86") > > from the akpm-current tree. > > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree > is submitted for merging. You may also want to consider cooperating > with the maintainer of the conflicting tree to minimise any particularly > complex conflicts. > > Note that I put the selects in their correct alphabetical position as > asked by the comment higher up in the file. If that had been done in > the patches, then there would have been no conflicts ... True.  Thanks, Stephan.  Before moving it to "its proper location", I'm wondering if there should be a separate section for "imply". Mimi