From: Andreas Schwab <schwab@linux-m68k.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Greg Ungerer <gerg@linux-m68k.org>, Jann Horn <jannh@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] binfmt_flat: make load_flat_shared_library() work
Date: Wed, 29 May 2019 15:16:38 +0200 [thread overview]
Message-ID: <mvma7f5bdu1.fsf@linux-m68k.org> (raw)
In-Reply-To: <7cac8be1-1667-6b6e-d2b8-d6ec5dc6da09@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Wed, 29 May 2019 14:32:04 +0200")
On Mai 29 2019, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
> On 5/28/19 12:56 PM, Greg Ungerer wrote:
>>> Maybe... but I didn't want to rip it out without having one of the
>>> maintainers confirm that this really isn't likely to be used anymore.
>>
>> I have not used shared libraries on m68k non-mmu setups for
>> a very long time. At least 10 years I would think.
> We use shared libraries in Debian on m68k and Andreas Schwab uses them
> on openSUSE/m68k.
Nope, I don't use non-mmu.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-m68k@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Arnd Bergmann <arnd@arndb.de>, Jann Horn <jannh@google.com>,
kernel list <linux-kernel@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Ungerer <gerg@linux-m68k.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] binfmt_flat: make load_flat_shared_library() work
Date: Wed, 29 May 2019 15:16:38 +0200 [thread overview]
Message-ID: <mvma7f5bdu1.fsf@linux-m68k.org> (raw)
In-Reply-To: <7cac8be1-1667-6b6e-d2b8-d6ec5dc6da09@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Wed, 29 May 2019 14:32:04 +0200")
On Mai 29 2019, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
> On 5/28/19 12:56 PM, Greg Ungerer wrote:
>>> Maybe... but I didn't want to rip it out without having one of the
>>> maintainers confirm that this really isn't likely to be used anymore.
>>
>> I have not used shared libraries on m68k non-mmu setups for
>> a very long time. At least 10 years I would think.
> We use shared libraries in Debian on m68k and Andreas Schwab uses them
> on openSUSE/m68k.
Nope, I don't use non-mmu.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-29 13:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 20:18 [PATCH] binfmt_flat: make load_flat_shared_library() work Jann Horn
2019-05-24 20:18 ` Jann Horn
2019-05-25 21:43 ` Andrew Morton
2019-05-25 21:43 ` Andrew Morton
2019-05-27 13:38 ` Jann Horn
2019-05-27 13:38 ` Jann Horn
2019-05-27 14:37 ` Nicolas Pitre
2019-05-27 14:37 ` Nicolas Pitre
2019-05-28 10:56 ` Greg Ungerer
2019-05-28 10:56 ` Greg Ungerer
2019-05-28 10:56 ` Greg Ungerer
2019-05-29 11:52 ` Arnd Bergmann
2019-05-29 11:52 ` Arnd Bergmann
2019-05-28 10:56 ` Greg Ungerer
2019-05-28 10:56 ` Greg Ungerer
2019-05-28 10:56 ` Greg Ungerer
2019-05-29 12:05 ` Arnd Bergmann
2019-05-29 12:05 ` Arnd Bergmann
2019-05-29 12:29 ` Greg Ungerer
2019-05-29 12:29 ` Greg Ungerer
2019-05-29 13:41 ` Arnd Bergmann
2019-05-29 13:41 ` Arnd Bergmann
2019-06-02 7:21 ` Sergei Poselenov
2019-06-02 7:21 ` Sergei Poselenov
2019-05-29 12:32 ` John Paul Adrian Glaubitz
2019-05-29 12:32 ` John Paul Adrian Glaubitz
2019-05-29 12:32 ` John Paul Adrian Glaubitz
2019-05-29 12:38 ` Jann Horn
2019-05-29 12:38 ` Jann Horn
2019-05-29 12:47 ` John Paul Adrian Glaubitz
2019-05-29 12:47 ` John Paul Adrian Glaubitz
2019-05-29 12:40 ` Greg Ungerer
2019-05-29 12:40 ` Greg Ungerer
2019-05-29 13:16 ` Andreas Schwab [this message]
2019-05-29 13:16 ` Andreas Schwab
2019-05-29 13:18 ` John Paul Adrian Glaubitz
2019-05-29 13:18 ` John Paul Adrian Glaubitz
[not found] ` <20190529131501.A44162183F@mail.kernel.org>
2019-05-29 14:09 ` Jann Horn
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=mvma7f5bdu1.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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.