Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp2687228ybh; Mon, 9 Mar 2020 10:55:16 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvg9ClLnPal7+hzIaDbuGX4dPlL9c0dFpmbv34IOxfvY3Ztv9uWWen3aV76nge/Gxp05iHe X-Received: by 2002:a9d:7458:: with SMTP id p24mr2139583otk.197.1583776516382; Mon, 09 Mar 2020 10:55:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583776516; cv=none; d=google.com; s=arc-20160816; b=jbsoYfRSr52YGyq9DwTVT647dnwzoCLg5ejtMh8NS0AxVQDXOn7F3TgYS3f+q+WWXz iJPiMOianIIxN89hOKTIkxXSCayVkwVWQs4YoJsptJ8Fdwzm3yRFgd4dZk5g93WjZ3YG wRbq65yfmMyFGNGN4350Ns8lRo7JHDMj+uLp89JnUkXWYQ3CIboYjnYcp8c4XPZFi1jF epaw1OXnYJxTxAd5tVOwdPm2cPdgYDlXQ+do99UpP8H5KJZ2IankMdPqts8naDT1PxMA Q7O66C7b5FtrFj9/BTlrmK02Av9J3KBEzH71H4o+/3WrDFt5PHJPDj4hmzNLNXsYKoyU 4S+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=YRxssQ3ei0rAiAxPncHOXYZdVjTj1kScBO3qHRsCQys=; b=mziBeKAu7QmD35/ohBBxYzMW0AnJIQ6WLivnisbiJj7TBvap0V/pLUtQana3SbyVco 5DKx7ZOKx4O6jGox5MArrMcD6nsKsScl4v7KNUSIJ63TZz5o6vOMuEMWMU4I50O+gKeZ nODh45IeMlyL77zpamkelxuretwPV2fxKa0QpjxGYDRU5/x/du+1c0aovNiv/BFl+lkY 46OUTmy8nFAmSjso9pOHazmq0RMddt7jhZfqYvBDbmZ/E3HD8dvz8N6AAcj3fTBg4yOF q6UYWgmvr+unjPl9eTh28WpfxQOql9LWMi+Ty//f0Fch5VvAqukc7fFltMg5qeT7x+Cr ut6g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-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 k3si4372965oiw.147.2020.03.09.10.54.53; Mon, 09 Mar 2020 10:55:16 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-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-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726333AbgCIRwI (ORCPT + 99 others); Mon, 9 Mar 2020 13:52:08 -0400 Received: from foss.arm.com ([217.140.110.172]:55246 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726193AbgCIRwI (ORCPT ); Mon, 9 Mar 2020 13:52:08 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 743421FB; Mon, 9 Mar 2020 10:52:07 -0700 (PDT) Received: from arrakis.emea.arm.com (arrakis.cambridge.arm.com [10.1.196.71]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id DC8933F67D; Mon, 9 Mar 2020 10:52:05 -0700 (PDT) Date: Mon, 9 Mar 2020 17:52:03 +0000 From: Catalin Marinas To: Mark Brown Cc: Ard Biesheuvel , Herbert Xu , "David S. Miller" , Will Deacon , Marc Zyngier , James Morse , Julien Thierry , Suzuki K Poulose , kvmarm , linux-arm-kernel , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" Subject: Re: [PATCH 12/18] arm64: kernel: Convert to modern annotations for assembly functions Message-ID: <20200309175203.GE4124965@arrakis.emea.arm.com> References: <20200218195842.34156-1-broonie@kernel.org> <20200218195842.34156-13-broonie@kernel.org> <20200228133718.GB4019108@arrakis.emea.arm.com> <20200228152219.GA4956@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200228152219.GA4956@sirena.org.uk> Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Fri, Feb 28, 2020 at 03:22:19PM +0000, Mark Brown wrote: > On Fri, Feb 28, 2020 at 01:37:18PM +0000, Catalin Marinas wrote: > > I wonder whether it would be easier to merge all these patches at > > 5.7-rc1, once most of the major changes went in. > > Only thing I can think that doing that might cause issue with is if > people are doing work that's not likely to make it in this cycle then > it'd be some extra rebasing or carrying of out of tree patches they'd > need to do (plus obviously this series might pick up new conflicts > itself). It's not a completely automated process unfortunately, > especially with trying to fix up some of the problems with the existing > annotations changing the output. But yeah, we could do that. I queued this series for 5.7, apart from patch 12. I'll try to fix any conflicts with whatever patches I'm adding but may drop some of them if they conflict badly with code in -next (not likely). We'll revisit at -rc1 to see what's left. Thanks. -- Catalin