From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 73AF7C43461 for ; Wed, 9 Sep 2020 06:55:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4052121741 for ; Wed, 9 Sep 2020 06:55:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725932AbgIIGzT (ORCPT ); Wed, 9 Sep 2020 02:55:19 -0400 Received: from verein.lst.de ([213.95.11.211]:55983 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725864AbgIIGzT (ORCPT ); Wed, 9 Sep 2020 02:55:19 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id B53AA6736F; Wed, 9 Sep 2020 08:55:15 +0200 (CEST) Date: Wed, 9 Sep 2020 08:55:15 +0200 From: Christoph Hellwig To: Palmer Dabbelt , viro@zeniv.linux.org.uk, Arnd Bergmann Cc: Christoph Hellwig , Paul Walmsley , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org Subject: Re: remove set_fs for riscv v2 Message-ID: <20200909065515.GA9618@lst.de> References: <20200907055825.1917151-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-arch-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org On Tue, Sep 08, 2020 at 09:59:29PM -0700, Palmer Dabbelt wrote: >> >> The first four patches are general improvements and enablement for all nommu >> ports, and might make sense to merge through the above base branch. > > Seems like it to me. These won't work without the SET_FS code so I'm OK if you > guys want to keep them all together. Otherwise I think I'd need to wait until > the SET_FS stuff gets merged before taking any of these, which would be a bit > of a headache. now that we've sorted out a remaining issue base.set_fs should not be rebased any more, so you could pull it into the riscv tree or a topic branch. The first four patch should go into base.set_fs, though. Arnd, can you re-review the updated patches?