From: Christoph Hellwig <hch@lst.de>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Christoph Hellwig <hch@lst.de>,
viro@zeniv.linux.org.uk, Arnd Bergmann <arnd@arndb.de>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: remove set_fs for riscv v2
Date: Tue, 29 Sep 2020 20:03:39 +0200 [thread overview]
Message-ID: <20200929180339.GA12546@lst.de> (raw)
In-Reply-To: <mhng-a034d2ee-67eb-4432-be9e-66fff000acda@palmerdabbelt-glaptop1>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-arch@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: remove set_fs for riscv v2
Date: Tue, 29 Sep 2020 20:03:39 +0200 [thread overview]
Message-ID: <20200929180339.GA12546@lst.de> (raw)
In-Reply-To: <mhng-a034d2ee-67eb-4432-be9e-66fff000acda@palmerdabbelt-glaptop1>
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.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2020-09-29 18:03 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 5:58 remove set_fs for riscv v2 Christoph Hellwig
2020-09-07 5:58 ` Christoph Hellwig
2020-09-07 5:58 ` [PATCH 1/8] uaccess: provide a generic TASK_SIZE_MAX definition Christoph Hellwig
2020-09-07 5:58 ` Christoph Hellwig
2020-09-07 5:58 ` [PATCH 2/8] asm-generic: improve the nommu {get,put}_user handling Christoph Hellwig
2020-09-07 5:58 ` Christoph Hellwig
2020-09-07 5:58 ` [PATCH 3/8] asm-generic: add nommu implementations of __{get,put}_kernel_nofault Christoph Hellwig
2020-09-07 5:58 ` [PATCH 3/8] asm-generic: add nommu implementations of __{get, put}_kernel_nofault Christoph Hellwig
2020-09-07 5:58 ` [PATCH 4/8] asm-generic: make the set_fs implementation optional Christoph Hellwig
2020-09-07 5:58 ` Christoph Hellwig
2020-09-07 5:58 ` [PATCH 5/8] riscv: use memcpy based uaccess for nommu again Christoph Hellwig
2020-09-07 5:58 ` Christoph Hellwig
2020-09-09 4:59 ` Palmer Dabbelt
2020-09-09 4:59 ` Palmer Dabbelt
2020-09-07 5:58 ` [PATCH 6/8] riscv: refactor __get_user and __put_user Christoph Hellwig
2020-09-07 5:58 ` Christoph Hellwig
2020-09-09 4:59 ` Palmer Dabbelt
2020-09-09 4:59 ` Palmer Dabbelt
2020-09-07 5:58 ` [PATCH 7/8] riscv: implement __get_kernel_nofault and __put_user_nofault Christoph Hellwig
2020-09-07 5:58 ` Christoph Hellwig
2020-09-09 4:59 ` Palmer Dabbelt
2020-09-09 4:59 ` Palmer Dabbelt
2020-09-07 5:58 ` [PATCH 8/8] riscv: remove address space overrides using set_fs() Christoph Hellwig
2020-09-07 5:58 ` Christoph Hellwig
2020-09-09 4:59 ` Palmer Dabbelt
2020-09-09 4:59 ` Palmer Dabbelt
2020-09-09 4:59 ` remove set_fs for riscv v2 Palmer Dabbelt
2020-09-09 4:59 ` Palmer Dabbelt
2020-09-09 6:55 ` Christoph Hellwig
2020-09-09 6:55 ` Christoph Hellwig
2020-09-09 20:38 ` Palmer Dabbelt
2020-09-09 20:38 ` Palmer Dabbelt
2020-09-22 4:37 ` Christoph Hellwig
2020-09-22 4:37 ` Christoph Hellwig
2020-09-26 17:50 ` Palmer Dabbelt
2020-09-26 17:50 ` Palmer Dabbelt
2020-09-26 19:13 ` Arnd Bergmann
2020-09-26 19:13 ` Arnd Bergmann
2020-10-04 17:27 ` Palmer Dabbelt
2020-10-04 17:27 ` Palmer Dabbelt
2020-09-28 12:49 ` Christoph Hellwig
2020-09-28 12:49 ` Christoph Hellwig
2020-09-28 16:45 ` Palmer Dabbelt
2020-09-28 16:45 ` Palmer Dabbelt
2020-09-29 18:03 ` Christoph Hellwig [this message]
2020-09-29 18:03 ` Christoph Hellwig
2020-09-26 6:58 ` Christoph Hellwig
2020-09-26 6:58 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200929180339.GA12546@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.