remove set_fs for m68k

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: remove set_fs for m68k
From: Christoph Hellwig <hch@xxxxxx>
Date: Thu, 16 Sep 2021 09:03:59 +0200
Cc: Michael Schmitz <schmitzmic@xxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, linux-m68k@xxxxxxxxxxxxxxx

Hi all,

this series converts m68k to the new world where set_fs is gone to make
the uaccess routines work on kernel pointers.

Changes from the RFC version:
  - simplify virt_to_phys_slow (and thus flush_icache_range)

Follow-Ups:
- Re: remove set_fs for m68k
  - From: Michael Schmitz
- [PATCH 6/6] m68k: remove set_fs()
  - From: Christoph Hellwig
- [PATCH 5/6] m68k: provide __{get,put}_kernel_nofault
  - From: Christoph Hellwig
- [PATCH 4/6] m68k: factor the 8-byte lowlevel {get,put}_user code into helpers
  - From: Christoph Hellwig
- [PATCH 3/6] m68k: use BUILD_BUG for passing invalid sizes to get_user/put_user
  - From: Christoph Hellwig
- [PATCH 2/6] m68k: remove the 030 case in virt_to_phys_slow
  - From: Christoph Hellwig
- [PATCH 1/6] m68k: document that access_ok is broken for !CONFIG_CPU_HAS_ADDRESS_SPACES
  - From: Christoph Hellwig

Prev by Date: [GIT PULL] m68k updates for v5.15 (take two)
Next by Date: [PATCH 1/6] m68k: document that access_ok is broken for !CONFIG_CPU_HAS_ADDRESS_SPACES
Previous by thread: [GIT PULL] m68k updates for v5.15 (take two)
Next by thread: [PATCH 1/6] m68k: document that access_ok is broken for !CONFIG_CPU_HAS_ADDRESS_SPACES
Index(es):
- Date
- Thread

[Index of Archives] [Video for Linux] [Yosemite News] [Linux S/390] [Linux Kernel] [Linux SCSI]

Powered by Linux