[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200929180339.GA12546@lst.de>
Date: Tue, 29 Sep 2020 20:03:39 +0200
From: Christoph Hellwig <hch@....de>
To: Palmer Dabbelt <palmer@...belt.com>
Cc: Christoph Hellwig <hch@....de>, viro@...iv.linux.org.uk,
Arnd Bergmann <arnd@...db.de>,
Paul Walmsley <paul.walmsley@...ive.com>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org
Subject: Re: remove set_fs for riscv v2
On Mon, Sep 28, 2020 at 09:45:30AM -0700, Palmer Dabbelt wrote:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git/log/?h=riscv-remove_set_fs
>>>
>>> under the assumption it might get lost otherwise, but let me know if that's not
>>> what you were looking for.
>>
>> Well, we'll want it in linux-next and then 5.10. Either a merge through
>> the RISC-V maintainer, or as part of the base branch from Al would
>> make sense to me.
>
> Sorry, I guess my question was really: does that branch have all the
> dependencies necessary for the RISC-V stuff to actually work? IIRC this actual
> patch set depended on some other one, and while I thinK I got everything I
> don't want to pull in something broken.
The riscv patchset depend only on the base.set_fs branch in Als tree.
Powered by blists - more mailing lists