From: Lukas Wunner <lukas@wunner.de>
To: Tony Hutter <hutter2@llnl.gov>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
corey@minyard.net, alok.a.tiwari@oracle.com,
mariusz.tkaczyk@linux.intel.com, minyard@acm.org,
linux-pci@vger.kernel.org,
openipmi-developer@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6] Introduce Cray ClusterStor E1000 NVMe slot LED driver
Date: Sun, 23 Nov 2025 17:35:19 +0100 [thread overview]
Message-ID: <aSM3x-V4Apcybpax@wunner.de> (raw)
In-Reply-To: <aQMsVUCBDF7ZUSK-@wunner.de>
On Thu, Oct 30, 2025 at 10:13:57AM +0100, Lukas Wunner wrote:
> On Wed, Oct 08, 2025 at 04:48:22PM -0700, Tony Hutter wrote:
> > @@ -376,8 +383,16 @@ int __init pcie_hp_init(void)
> >
> > retval = pcie_port_service_register(&hpdriver_portdrv);
> > pr_debug("pcie_port_service_register = %d\n", retval);
> > - if (retval)
> > + if (retval) {
> > pr_debug("Failure to register service\n");
> > + return retval;
> > + }
> > +
> > +#ifdef CONFIG_HOTPLUG_PCI_PCIE_CRAY_E1000
> > + retval = craye1k_init();
> > + if (retval)
> > + pr_debug("Failure to register Cray E1000 extensions");
> > +#endif
>
> You also need to annotate craye1k_init() with __init.
Sorry, I've realized that I made the following note during review
of your patch but forgot to include it in the reply above:
You may want to consider making this driver modular and auto-load it
using a MODULE_DEVICE_TABLE(dmi, ...) declaration. craye1k_init()
would then become the module_init() call and you could tear down
everything in a module_exit() call. If you want to run craye1k_init()
earlier if built-in, use e.g. an arch_initcall() instead of a
module_init() call. There's precedent in the tree for combinations
of arch_initcall() + module_exit().
Thanks,
Lukas
next prev parent reply other threads:[~2025-11-23 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 23:48 [PATCH v6] Introduce Cray ClusterStor E1000 NVMe slot LED driver Tony Hutter
2025-10-30 9:13 ` Lukas Wunner
2025-11-23 16:35 ` Lukas Wunner [this message]
2025-12-09 1:31 ` Tony Hutter
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=aSM3x-V4Apcybpax@wunner.de \
--to=lukas@wunner.de \
--cc=alok.a.tiwari@oracle.com \
--cc=corey@minyard.net \
--cc=helgaas@kernel.org \
--cc=hutter2@llnl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.