[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20241218162827.750d7f4a28c9f8888ec9711a@linux-foundation.org>
Date: Wed, 18 Dec 2024 16:28:27 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Martin Kepplinger <martink@...teo.de>
Cc: joel.granados@...nel.org, linux-kernel@...r.kernel.org, Christoph
Hellwig <hch@....de>
Subject: Re: [PATCH] init: fix removal warning for deprecated initrd loading
On Wed, 18 Dec 2024 12:36:38 +0000 Martin Kepplinger <martink@...teo.de> wrote:
> This won't be removed in 2021, no matter how hard we try.
>
man git-timetravel
> ...
>
> --- a/init/do_mounts_initrd.c
> +++ b/init/do_mounts_initrd.c
> @@ -89,7 +89,7 @@ static void __init handle_initrd(char *root_device_name)
> extern char *envp_init[];
> int error;
>
> - pr_warn("using deprecated initrd support, will be removed in 2021.\n");
> + pr_warn("using deprecated initrd support, will be removed soon.\n");
>
> real_root_dev = new_encode_dev(ROOT_DEV);
> create_dev("/dev/root.old", Root_RAM0);
Well, what's stopping us from removing initrd support?
Maybe the next step is to remove it by default, with a hard-to-find
Kconfig setting to get it back again?
Powered by blists - more mailing lists