linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-sh@vger.kernel.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH 0/2] sh: get rid of __ARCH_USE_5LEVEL_HACK
Date: Tue, 17 Dec 2019 10:15:49 -0500	[thread overview]
Message-ID: <20191217151549.GH1666@brightrain.aerifal.cx> (raw)
In-Reply-To: <20191217142150.10392-1-rppt@kernel.org>

On Tue, Dec 17, 2019 at 04:21:48PM +0200, Mike Rapoport wrote:
> From: Mike Rapoport <rppt@linux.ibm.com>
> 
> Hi,
> 
> These patches update the SuperH page table folding/unfolding to take into
> account the 5th level.

Is this only for 64-bit/sh5? If so, I'd really like to avoid having
patch churn that nominally keeps it working, since it doesn't; GCC
dropped support a long time ago and it was experimental to begin with,
never appeared in production. Has anyone looked lately at what it
would take to remove it?

Rich

  parent reply	other threads:[~2019-12-17 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 14:21 [PATCH 0/2] sh: get rid of __ARCH_USE_5LEVEL_HACK Mike Rapoport
2019-12-17 14:21 ` [PATCH 1/2] sh: drop __pXd_offset() macros that duplicate pXd_index() ones Mike Rapoport
2019-12-17 14:21 ` [PATCH 2/2] sh: add support for folded p4d page tables Mike Rapoport
2019-12-17 17:59   ` Geert Uytterhoeven
2019-12-17 18:32     ` Mike Rapoport
2019-12-17 15:15 ` Rich Felker [this message]
2019-12-17 15:36   ` [PATCH 0/2] sh: get rid of __ARCH_USE_5LEVEL_HACK Mike Rapoport

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=20191217151549.GH1666@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=rppt@linux.ibm.com \
    --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).