From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Henderson Subject: Re: [PATCH 6/6] s390x: Mark archrandom.h functions __must_check Date: Tue, 29 Oct 2019 14:18:33 +0100 Message-ID: References: <20191028210559.8289-1-rth@twiddle.net> <20191028210559.8289-7-rth@twiddle.net> <935cf73a-d06c-365d-131a-23dcb350ba17@linux.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <935cf73a-d06c-365d-131a-23dcb350ba17@linux.ibm.com> Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Harald Freudenberger , linux-arch@vger.kernel.org Cc: linux-s390@vger.kernel.org, Vasily Gorbik , x86@kernel.org, Heiko Carstens , Christian Borntraeger , linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org List-Id: linux-arch.vger.kernel.org On 10/29/19 8:26 AM, Harald Freudenberger wrote: > Fine with me, Thanks, reviewed, build and tested. > You may add my reviewed-by: Harald Freudenberger > However, will this go into the kernel tree via crypto or s390 subsystem ? That's an excellent question. As an API decision, perhaps going via crypto makes more sense, but none of the patches are dependent on one another, so they could go through separate architecture trees. It has been a long time since I have done much kernel work; I'm open to suggestions on the subject. r~ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-f195.google.com ([209.85.214.195]:40604 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388166AbfJ2NSz (ORCPT ); Tue, 29 Oct 2019 09:18:55 -0400 Received: by mail-pl1-f195.google.com with SMTP id p5so2427317plr.7 for ; Tue, 29 Oct 2019 06:18:55 -0700 (PDT) Subject: Re: [PATCH 6/6] s390x: Mark archrandom.h functions __must_check References: <20191028210559.8289-1-rth@twiddle.net> <20191028210559.8289-7-rth@twiddle.net> <935cf73a-d06c-365d-131a-23dcb350ba17@linux.ibm.com> From: Richard Henderson Message-ID: Date: Tue, 29 Oct 2019 14:18:33 +0100 MIME-Version: 1.0 In-Reply-To: <935cf73a-d06c-365d-131a-23dcb350ba17@linux.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: Harald Freudenberger , linux-arch@vger.kernel.org Cc: x86@kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Heiko Carstens , Vasily Gorbik , Christian Borntraeger Message-ID: <20191029131833.EJcrAuZOSTaB5fADPGXFEOr04fXs9W2m1VCJ--ZGrnM@z> On 10/29/19 8:26 AM, Harald Freudenberger wrote: > Fine with me, Thanks, reviewed, build and tested. > You may add my reviewed-by: Harald Freudenberger > However, will this go into the kernel tree via crypto or s390 subsystem ? That's an excellent question. As an API decision, perhaps going via crypto makes more sense, but none of the patches are dependent on one another, so they could go through separate architecture trees. It has been a long time since I have done much kernel work; I'm open to suggestions on the subject. r~