From: Christoph Hellwig <hch@lst.de>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, hch@lst.de
Subject: Re: [PATCH v3 4/4] MIPS: Remove get_fs/set_fs
Date: Thu, 1 Apr 2021 16:05:07 +0200 [thread overview]
Message-ID: <20210401140507.GB24331@lst.de> (raw)
In-Reply-To: <20210401125639.42963-5-tsbogend@alpha.franken.de>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2021-04-01 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 12:56 [PATCH v3 0/4] MIPS: Remove get_fs/set_fs Thomas Bogendoerfer
2021-04-01 12:56 ` [PATCH v3 1/4] MIPS: kernel: Remove not needed set_fs calls Thomas Bogendoerfer
2021-04-01 12:56 ` [PATCH v3 2/4] MIPS: uaccess: Added __get/__put_kernel_nofault Thomas Bogendoerfer
2021-04-01 12:56 ` [PATCH v3 3/4] MIPS: uaccess: Remove get_fs/set_fs call sites Thomas Bogendoerfer
2021-04-01 14:04 ` Christoph Hellwig
2021-04-01 12:56 ` [PATCH v3 4/4] MIPS: Remove get_fs/set_fs Thomas Bogendoerfer
2021-04-01 14:05 ` Christoph Hellwig [this message]
2021-04-06 7:24 ` [PATCH v3 0/4] " Christoph Hellwig
2021-04-06 13:01 ` Thomas Bogendoerfer
2021-04-06 12:59 ` Thomas Bogendoerfer
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=20210401140507.GB24331@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).