From: Finn Thain <fthain@linux-m68k.org>
To: Michael Ellerman <michaele@au1.ibm.com>
Cc: "ukrishn@linux.ibm.com" <ukrishn@linux.ibm.com>,
Andrew Donnellan <ajd@linux.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"manoj@linux.ibm.com" <manoj@linux.ibm.com>,
"fbarrat@linux.ibm.com" <fbarrat@linux.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: Make cxl obsolete
Date: Thu, 11 Apr 2024 09:43:48 +1000 (AEST) [thread overview]
Message-ID: <cf03bfb4-0970-fe3a-062f-8c4e371a7afa@linux-m68k.org> (raw)
In-Reply-To: <87o7aha1mj.fsf@mail.lhotse>
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.
next prev parent reply other threads:[~2024-04-10 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 3:10 [PATCH 1/2] MAINTAINERS: Make cxlflash obsolete Andrew Donnellan
2024-04-09 3:10 ` [PATCH 2/2] MAINTAINERS: Make cxl obsolete Andrew Donnellan
2024-04-09 4:37 ` Michael Ellerman
2024-04-09 5:53 ` Christophe Leroy
2024-04-10 11:38 ` Michael Ellerman
2024-04-10 23:43 ` Finn Thain [this message]
2024-05-03 3:15 ` Andrew Donnellan
2024-05-03 7:55 ` Andrew Donnellan
2024-05-03 10:31 ` Michael Ellerman
2024-04-25 1:57 ` [PATCH 1/2] MAINTAINERS: Make cxlflash obsolete Martin K. Petersen
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=cf03bfb4-0970-fe3a-062f-8c4e371a7afa@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=ajd@linux.ibm.com \
--cc=fbarrat@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manoj@linux.ibm.com \
--cc=michaele@au1.ibm.com \
--cc=ukrishn@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).