From: Sven Joachim <svenjoac@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ian Kent <raven@themaw.net>,
autofs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/*/configs/*defconfig: Replace AUTOFS4_FS by AUTOFS_FS
Date: Sun, 30 Jul 2023 08:06:16 +0200 [thread overview]
Message-ID: <87sf96kk6f.fsf@turtle.gmx.de> (raw)
In-Reply-To: <CAHk-=wgK9-Tx4BxYMrc0pg==mcaz3cjWF6-CBwVpM_BZAmf4JQ@mail.gmail.com> (Linus Torvalds's message of "Sat, 29 Jul 2023 14:07:41 -0700")
On 2023-07-29 14:07 -0700, Linus Torvalds wrote:
> On Thu, 27 Jul 2023 at 13:01, Sven Joachim <svenjoac@gmx.de> wrote:
>>
>> Commit a2225d931f75 ("autofs: remove left-over autofs4 stubs")
>> promised the removal of the fs/autofs/Kconfig fragment for AUTOFS4_FS
>> within a couple of releases, but five years later this still has not
>> happened yet, and AUTOFS4_FS is still enabled in 63 defconfigs.
>
> Ok, I ran the script, and also decided that we might as well remove
> the AUTOFS4 legacy naming stub entry by now.
>
> It has been five years, and people will have either picked up the new
> name with 'make oldconfig', or they just don't use 'make oldconfig' at
> all.
I had not added the suggested the removal of AUTOFS4_FS from the Kconfig
in my patch, because some projects seem to have have copy-pasted from
the kernel's defconfig files, e.g. systemd[1]. Hopefully not a big deal
for actual users, but worth mentioning.
Cheers,
Sven
1. https://github.com/systemd/systemd/pull/28561
next prev parent reply other threads:[~2023-07-30 6:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 20:00 [PATCH] arch/*/configs/*defconfig: Replace AUTOFS4_FS by AUTOFS_FS Sven Joachim
2023-07-28 1:15 ` Ian Kent
2023-07-29 21:07 ` Linus Torvalds
2023-07-30 0:27 ` Ian Kent
2023-07-30 6:06 ` Sven Joachim [this message]
2023-07-30 7:20 ` Ian Kent
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=87sf96kk6f.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=autofs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=torvalds@linux-foundation.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