From: Lee Jones <lee@kernel.org>
To: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Cc: linux-pci@vger.kernel.org, linux-leds@vger.kernel.org,
"Lukas Wunner" <lukas@wunner.de>,
"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 10:03:40 +0100 [thread overview]
Message-ID: <20240909090340.GA6556@google.com> (raw)
In-Reply-To: <20240904104848.23480-2-mariusz.tkaczyk@linux.intel.com>
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.
>
> Suggested-by: Dan Williams <dan.j.williams@intel.com>
Do you have a link to this discussion?
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
> ---
> drivers/Makefile | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/Makefile b/drivers/Makefile
> index fe9ceb0d2288..45d1c3e630f7 100644
> --- 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
This seems very fragile.
Isn't there a better way to describe the dependency in Kconfig etc?
> +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/
> --
> 2.35.3
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-09-09 9:03 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 [this message]
2024-09-09 9:28 ` Mariusz Tkaczyk
2024-09-09 20:21 ` Lukas Wunner
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=20240909090340.GA6556@google.com \
--to=lee@kernel.org \
--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=linux-leds@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--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 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.