From: Borislav Petkov <bp@alien8.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: x86@kernel.org, linux-mm@kvack.org,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: drop entry to removed file in EXEC & BINFMT API
Date: Wed, 16 Mar 2022 08:48:14 +0100 [thread overview]
Message-ID: <YjGWPh6MSLqeL47e@zn.tnic> (raw)
In-Reply-To: <20220316050828.17255-1-lukas.bulwahn@gmail.com>
On Wed, Mar 16, 2022 at 06:08:28AM +0100, Lukas Bulwahn wrote:
> Commit f9444ea5e208 ("x86: Remove a.out support") removes
> arch/x86/ia32/ia32_aout.c, but misses a reference to that file in
> MAINTAINERS.
It seems we're keeping a.out after all:
https://lore.kernel.org/r/4c449fab-8135-5057-7d2c-7b948ce130cc@theinnocuous.com
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-03-16 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 5:08 Lukas Bulwahn
2022-03-16 7:48 ` Borislav Petkov [this message]
2022-03-16 8:12 ` Lukas Bulwahn
2022-03-16 9:02 ` Borislav Petkov
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=YjGWPh6MSLqeL47e@zn.tnic \
--to=bp@alien8.de \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lukas.bulwahn@gmail.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox