From: Pavel Machek <pavel@ucw.cz>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Lee Jones <lee@kernel.org>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v2 2/2] leds: max597x: Add support for max597x
Date: Fri, 24 Mar 2023 14:07:02 +0100 [thread overview]
Message-ID: <ZB2gdvgFR4ZTIegA@duo.ucw.cz> (raw)
In-Reply-To: <688423c6-ba98-002c-efe5-7b0997d6af73@9elements.com>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
Hi!
> > > +++ b/drivers/leds/Kconfig
> > > @@ -590,6 +590,17 @@ config LEDS_ADP5520
> > > To compile this driver as a module, choose M here: the
> > > module will
> > > be called leds-adp5520.
> > > +config LEDS_MAX597X
> > > + tristate "LED Support for Maxim 597x"
> > > + depends on LEDS_CLASS
> > > + depends on MFD_MAX597X
> > > + help
> > > + This option enables support for the Maxim 597x smart switch
> > > indication LEDs
> > > + via the I2C bus.
> > > +
> > > + To compile this driver as a module, choose M here: the module will
> > > + be called max597x-led.
> >
> > leds-max597x?
> As per struct max597x_led_driver, driver name is max597x-led
Please test the modular build and double check the module name.
BR,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-03-24 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230323194550.1914725-1-Naresh.Solanki@9elements.com>
2023-03-23 19:45 ` [PATCH v2 2/2] leds: max597x: Add support for max597x Naresh Solanki
2023-03-23 20:18 ` Christophe JAILLET
2023-03-24 10:54 ` Naresh Solanki
2023-03-24 13:07 ` Pavel Machek [this message]
2023-03-24 13:50 ` Naresh Solanki
2023-03-24 15:36 ` Christophe JAILLET
2023-03-27 15:47 ` Naresh Solanki
2023-03-27 17:20 ` Christophe JAILLET
2023-03-27 17:49 ` Naresh Solanki
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=ZB2gdvgFR4ZTIegA@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=christophe.jaillet@wanadoo.fr \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.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