[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20260115120215.1575388b1f01776a8e2a8fbe@linux-foundation.org>
Date: Thu, 15 Jan 2026 12:02:15 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Harry Austen <hpausten@...tonmail.com>
Cc: Huacai Chen <chenhuacai@...nel.org>, linux-kernel@...r.kernel.org,
Lillian Berry <lillian@...r-ark.net>
Subject: Re: [PATCH] init/main.c: prevent warning on lack of default
implicit rdinit
On Wed, 14 Jan 2026 22:02:27 +0000 Harry Austen <hpausten@...tonmail.com> wrote:
> If rdinit was not explicitly provided on cmdline, and default /init does
> not exist, no warning should be printed.
Seems that we already have a very similar patch from Lillian:
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/init-mainc-check-if-rdinit-was-explicitly-set-before-printing-warning.patch
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/init-mainc-check-if-rdinit-was-explicitly-set-before-printing-warning-fix.patch
What's happening here?
Powered by blists - more mailing lists