From: Christoph Hellwig <hch@lst.de>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
"moderated list:H8/300 ARCHITECTURE"
<uclinux-h8-devel@lists.sourceforge.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: remove set_fs() for h8300
Date: Fri, 20 Aug 2021 16:33:37 +0200 [thread overview]
Message-ID: <20210820143337.GA30797@lst.de> (raw)
In-Reply-To: <CAK8P3a3rtL5t65GQOEP5XdfsaEOZP=PpiZM9hjYkO=jC6oOptA@mail.gmail.com>
On Fri, Aug 20, 2021 at 01:05:30PM +0200, Arnd Bergmann wrote:
> It took me a while to figure out that this works on architectures that
> define CONFIG_UACCESS_MEMCPY, as they get the asm-generic
> version of get_kernel_nofault(). Maybe add that to the changelog,
> plus my
>
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
>
> Do you have more of these? I'm happy to take them through the
> asm-generic tree, at least for architectures with no response from
> the maintainers (not m68k, which looks too complex). I did partial
> patches for sh and sparc at some point to remove the set_fs() callers,
> but got stuck when I tried doing ia64 and didn't submit any of these.
This one actually got picked up in the u8300 tree now. The only
outstanding one I have is uml, waiting for maintainer feedback for
that.
prev parent reply other threads:[~2021-08-20 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 11:53 remove set_fs() for h8300 Christoph Hellwig
2021-07-09 11:53 ` [PATCH 1/2] h8300: remove memory.c Christoph Hellwig
2021-07-09 11:53 ` [PATCH 2/2] h8300: don't implement set_fs Christoph Hellwig
2021-08-17 5:20 ` remove set_fs() for h8300 Christoph Hellwig
2021-08-20 11:05 ` Arnd Bergmann
2021-08-20 14:33 ` Christoph Hellwig [this message]
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=20210820143337.GA30797@lst.de \
--to=hch@lst.de \
--cc=arnd@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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.