From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752670AbdGLTel (ORCPT ); Wed, 12 Jul 2017 15:34:41 -0400 Received: from mail-oi0-f65.google.com ([209.85.218.65]:36625 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751161AbdGLTei (ORCPT ); Wed, 12 Jul 2017 15:34:38 -0400 MIME-Version: 1.0 In-Reply-To: <20170712175505.GG15191@arm.com> References: <20170712013130.14792-1-palmer@dabbelt.com> <20170712175505.GG15191@arm.com> From: Arnd Bergmann Date: Wed, 12 Jul 2017 21:34:36 +0200 X-Google-Sender-Auth: pbdQrGZmMnO_nrkbLS_wuwoc8vs Message-ID: Subject: Re: RISC-V Linux Port v6 To: Will Deacon Cc: Palmer Dabbelt , Olof Johansson , Andrew Morton , albert@sifive.com, Masahiro Yamada , Michal Marek , Peter Zijlstra , Boqun Feng , Ingo Molnar , Daniel Lezcano , Thomas Gleixner , Jason Cooper , Marc Zyngier , gregkh , Jiri Slaby , David Miller , Mauro Carvalho Chehab , Stephen Rothwell , =?UTF-8?B?RnLDqWTDqXJpYyBXZWlzYmVja2Vy?= , Al Viro , "Luis R. Rodriguez" , Doug Ledford , Bart Van Assche , sstabellini@kernel.org, Daniel Vetter , Michael Ellerman , Mark Salter , Nicolas Dichtel , James Hogan , Paul Gortmaker , Guenter Roeck , Heiko Carstens , Martin Schwidefsky , Linux Kernel Mailing List , patches@groups.riscv.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 12, 2017 at 7:55 PM, Will Deacon wrote: > On Wed, Jul 12, 2017 at 09:58:01AM +0200, Arnd Bergmann wrote: >> On Wed, Jul 12, 2017 at 3:31 AM, Palmer Dabbelt wrote: >> Without having looked at the current state of the patch series, I would >> guess that next week is a good time to ask for inclusion *in* linux-next, >> while continuing the review. > > My only concern about getting this into -next is that is sets expectations > that this is going to land in the next merge window, but we're unable to > review much of the atomics, barriers and locking code because the > architecture document is being rewritten and is not yet available: > > https://marc.info/?i=8709419e3d964b86b025bb35a6b55440%40HQMAIL105.nvidia.com I don't see that as a show-stopper for the merge: yes, the kernel port will need to conform to the architecture once we know what it is, but overall, this seems like a detail that can easily be fixed after the merge as no ABI is involved. The worst case here is that the initial release is a bit unstable, slow or both and this will get fixed later. I would expect this to be the case even if the atomics are all correct ;-) Arnd