[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cf03bfb4-0970-fe3a-062f-8c4e371a7afa@linux-m68k.org>
Date: Thu, 11 Apr 2024 09:43:48 +1000 (AEST)
From: Finn Thain <fthain@...ux-m68k.org>
To: Michael Ellerman <michaele@....ibm.com>
cc: Christophe Leroy <christophe.leroy@...roup.eu>,
Andrew Donnellan <ajd@...ux.ibm.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"fbarrat@...ux.ibm.com" <fbarrat@...ux.ibm.com>,
"ukrishn@...ux.ibm.com" <ukrishn@...ux.ibm.com>,
"manoj@...ux.ibm.com" <manoj@...ux.ibm.com>
Subject: Re: [PATCH 2/2] MAINTAINERS: Make cxl obsolete
On Wed, 10 Apr 2024, Michael Ellerman wrote:
> >
> > Could we do something similar, write a message at boottime when the
> > CXL driver gets probed ?
>
> Yeah, I think so.
>
> There's still the problem that people tend not to look at dmesg until
> something breaks, but at least we can try and get their attention.
>
People would get in the habit to look for that, if all maintainers adopted
a convention such that a boot-time message would list every newly-orphaned
driver in each release. Maybe the maintainer of the MAINTAINERS file could
check that every newly orphaned driver got announced.
Powered by blists - more mailing lists