From: Greg Ungerer <gerg@linux-m68k.org>
To: linux-m68k@vger.kernel.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, dalias@libc.org
Subject: Re: [PATCH v2 4/4] m68knommu: allow elf_fdpic loader to be selected
Date: Fri, 13 May 2022 09:57:43 +1000 [thread overview]
Message-ID: <b128ed0f-08f8-2742-e22c-20cc5870a61c@linux-m68k.org> (raw)
In-Reply-To: <20220512230602.1408871-1-gerg@linux-m68k.org>
On 13/5/22 09:06, Greg Ungerer wrote:
> The m68k architecture code is capable of supporting the binfmt_elf_fdpic
> loader, so allow it to be configured. It is restricted to nommu
> configurations at this time due to the MMU context structures/code not
> supporting everything elf_fdpic needs when MMU is enabled.
>
> Link: https://lore.kernel.org/linux-m68k/20220428033319.239341-1-gerg@linux-m68k.org/
> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
> ---
> fs/Kconfig.binfmt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> v2: remove superfluous surrounding "(" ")"
If no one has any objections I can carry this in the m68knommu
git tree with the rest of the series.
Regards
Greg
> diff --git a/fs/Kconfig.binfmt b/fs/Kconfig.binfmt
> index 21c6332fa785..fb325b3aa4b0 100644
> --- a/fs/Kconfig.binfmt
> +++ b/fs/Kconfig.binfmt
> @@ -58,7 +58,7 @@ config ARCH_USE_GNU_PROPERTY
> config BINFMT_ELF_FDPIC
> bool "Kernel support for FDPIC ELF binaries"
> default y if !BINFMT_ELF
> - depends on (ARM || (SUPERH && !MMU))
> + depends on ARM || ((M68K || SUPERH) && !MMU)
> select ELFCORE
> help
> ELF FDPIC binaries are based on ELF, but allow the individual load
prev parent reply other threads:[~2022-05-12 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 23:06 [PATCH v2 4/4] m68knommu: allow elf_fdpic loader to be selected Greg Ungerer
2022-05-12 23:57 ` Greg Ungerer [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=b128ed0f-08f8-2742-e22c-20cc5870a61c@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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.