From: Christoph Hellwig <hch@lst.de>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: uclinux-h8-devel@lists.sourceforge.jp, linux-kernel@vger.kernel.org
Subject: Re: remove set_fs() for h8300
Date: Tue, 17 Aug 2021 07:20:03 +0200 [thread overview]
Message-ID: <20210817052003.GA4595@lst.de> (raw)
In-Reply-To: <20210709115311.3424912-1-hch@lst.de>
On Fri, Jul 09, 2021 at 01:53:09PM +0200, Christoph Hellwig wrote:
> Hi all,
>
> this series removes support for the deprecated set_fs address space
> override on h8300. Because h8300 doesn't actually have different
> address spaces to start with as a pure nommu port the changes are
> pretty simple.
>
> Compile tested only.
Any comments?
next prev parent reply other threads:[~2021-08-17 5:20 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 ` Christoph Hellwig [this message]
2021-08-20 11:05 ` remove set_fs() for h8300 Arnd Bergmann
2021-08-20 14:33 ` 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=20210817052003.GA4595@lst.de \
--to=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).