From: Lukas Wunner <lukas@wunner.de>
To: Lee Jones <lee@kernel.org>
Cc: "Mariusz Tkaczyk" <mariusz.tkaczyk@linux.intel.com>,
linux-pci@vger.kernel.org, linux-leds@vger.kernel.org,
"Christoph Hellwig" <hch@lst.de>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Stuart Hayes" <stuart.w.hayes@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Dan Williams" <dan.j.williams@intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Keith Busch" <kbusch@kernel.org>,
"Marek Behun" <marek.behun@nic.cz>, "Pavel Machek" <pavel@ucw.cz>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v7 1/3] leds: Init leds class earlier
Date: Mon, 9 Sep 2024 22:21:16 +0200 [thread overview]
Message-ID: <Zt9YvMf2jVyaQfRo@wunner.de> (raw)
In-Reply-To: <20240909090340.GA6556@google.com>
On Mon, Sep 09, 2024 at 10:03:40AM +0100, Lee Jones wrote:
> On Wed, 04 Sep 2024, Mariusz Tkaczyk wrote:
> > NPEM driver will require leds class, there is an init-order conflict.
> > Make sure that LEDs initialization happens first and add comment.
[...]
> > --- a/drivers/Makefile
> > +++ b/drivers/Makefile
> > @@ -17,6 +17,9 @@ obj-$(CONFIG_PINCTRL) += pinctrl/
> > obj-$(CONFIG_GPIOLIB) += gpio/
> > obj-y += pwm/
> >
> > +# LEDs must come before PCI, it is needed by NPEM driver
> > +obj-y += leds/
> > +
> > obj-y += pci/
> >
> > obj-$(CONFIG_PARISC) += parisc/
> > @@ -130,7 +133,6 @@ obj-$(CONFIG_CPU_IDLE) += cpuidle/
> > obj-y += mmc/
> > obj-y += ufs/
> > obj-$(CONFIG_MEMSTICK) += memstick/
> > -obj-y += leds/
> > obj-$(CONFIG_INFINIBAND) += infiniband/
> > obj-y += firmware/
> > obj-$(CONFIG_CRYPTO) += crypto/
>
> This seems very fragile.
>
> Isn't there a better way to describe the dependency in Kconfig etc?
In v2 of this series, the correct init order was ensured by
running leds_init() at "arch" initcall level, instead of "subsys":
https://lore.kernel.org/linux-pci/20240528131940.16924-2-mariusz.tkaczyk@linux.intel.com/
If you prefer this alternative approach, then Bjorn or Krzysztof
can probably replace the commit on the pci.git/npem branch.
AFAIK, all topic branches in pci.git are to be considered drafts
that can be amended until the pull request is sent.
Thanks,
Lukas
next prev parent reply other threads:[~2024-09-09 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 10:48 [PATCH v7 0/3] PCIe Enclosure LED Management Mariusz Tkaczyk
2024-09-04 10:48 ` [PATCH v7 1/3] leds: Init leds class earlier Mariusz Tkaczyk
2024-09-09 9:03 ` Lee Jones
2024-09-09 9:28 ` Mariusz Tkaczyk
2024-09-09 20:21 ` Lukas Wunner [this message]
2024-09-04 10:48 ` [PATCH v7 2/3] PCI/NPEM: Add Native PCIe Enclosure Management support Mariusz Tkaczyk
2024-09-04 10:48 ` [PATCH v7 3/3] PCI/NPEM: Add _DSM PCIe SSD status LED management Mariusz Tkaczyk
2024-09-06 6:48 ` Krzysztof Wilczyński
2024-09-04 22:27 ` [PATCH v7 0/3] PCIe Enclosure LED Management Bjorn Helgaas
2024-09-05 8:38 ` Andy Shevchenko
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=Zt9YvMf2jVyaQfRo@wunner.de \
--to=lukas@wunner.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kbusch@kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=pavel@ucw.cz \
--cc=rdunlap@infradead.org \
--cc=stuart.w.hayes@gmail.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