From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, Richard Purdie <rpurdie@rpsys.net>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: netxbig: fix module autoload for OF registration
Date: Tue, 29 Nov 2016 16:34:43 +0100 [thread overview]
Message-ID: <b4bf0179-0dde-0500-b07f-96bb95c78a99@samsung.com> (raw)
In-Reply-To: <9f84c025-7835-1664-60df-092b80a4ade7@osg.samsung.com>
Hi Javier,
On 11/29/2016 04:00 PM, Javier Martinez Canillas wrote:
> Hello Jacek,
>
> On 10/21/2016 12:52 PM, Javier Martinez Canillas wrote:
>> If the driver is built as a module, autoload won't work because the module
>> alias information is not filled. So user-space can't match the registered
>> device with the corresponding module.
>>
>> Export the module alias information using the MODULE_DEVICE_TABLE() macro.
>>
>> Before this patch:
>>
>> $ modinfo drivers/leds//leds-netxbig.ko | grep alias
>> alias: platform:leds-netxbig
>>
>> After this patch:
>>
>> $ modinfo drivers/leds//leds-netxbig.ko | grep alias
>> alias: platform:leds-netxbig
>> alias: of:N*T*Clacie,netxbig-ledsC*
>> alias: of:N*T*Clacie,netxbig-leds
>>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>> ---
>>
>
> Any comments about this patch?
I mistakenly marked it as merged. Sorry about that.
Applied to the for-next branch of linux-leds.git.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2016-11-29 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 15:52 [PATCH] leds: netxbig: fix module autoload for OF registration Javier Martinez Canillas
2016-11-29 15:00 ` Javier Martinez Canillas
2016-11-29 15:34 ` Jacek Anaszewski [this message]
2016-11-29 15:38 ` Javier Martinez Canillas
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=b4bf0179-0dde-0500-b07f-96bb95c78a99@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.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 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).