From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, airlied@linux.ie,
dri-devel@lists.freedesktop.org, akpm@linux-foundation.org
Subject: Re: [RESEND] drm: imx: imx-tve: Fix module autoload for OF platform driver
Date: Mon, 30 Nov 2015 21:56:05 +0000 [thread overview]
Message-ID: <565CC5F5.9070908@osg.samsung.com> (raw)
In-Reply-To: <1448918893.3890.45.camel@pengutronix.de>
On 30/11/15 21:28, Philipp Zabel wrote:
> Hi Luis,
>
> thanks for the reminder.
>
No problem. I was worried I was bothering.
> Am Montag, den 30.11.2015, 15:02 +0000 schrieb Luis de Bethencourt:
>> This platform driver has a OF device ID table but the OF module
>> alias information is not created so module autoloading won't work.
>>
>> Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
>> ---
>>
>> Hi,
>>
>> This is a resend of a patch from October 20th [0]
>
> Sorry to have missed it, I was in the middle of a vacation then.
> I've applied it to my fixes branch now.
>
I understand, we all have a few emails that fall between the cracks.
Thank you very much for reviewing and applying.
Luis
>> I am adding Andrew Morton to the CC list as was recommended at the Korea Linux
>> Forum.
>>
>> This patch adds the missing MODULE_DEVICE_TABLE() for OF to export
>> that information so modules have the correct aliases built-in and
>> autoloading works correctly.
>>
>> A longer explanation by Javier Canillas can be found here:
>> https://lkml.org/lkml/2015/7/30/519
>> A multitude of similar patches have been merged for other drivers, search
>> the git log for "module autoload for OF platform driver".
>>
>> Thanks,
>> Luis
>
> regards
> Philipp
>
prev parent reply other threads:[~2015-11-30 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 15:02 [RESEND] drm: imx: imx-tve: Fix module autoload for OF platform driver Luis de Bethencourt
2015-11-30 21:28 ` Philipp Zabel
2015-11-30 21:56 ` Luis de Bethencourt [this message]
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=565CC5F5.9070908@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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