Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752845AbbH2Krb (ORCPT ); Sat, 29 Aug 2015 06:47:31 -0400 Received: from mail-wi0-f181.google.com ([209.85.212.181]:38547 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751963AbbH2Kr2 (ORCPT ); Sat, 29 Aug 2015 06:47:28 -0400 Date: Sat, 29 Aug 2015 12:47:26 +0200 From: Luis de Bethencourt To: linux-kernel@vger.kernel.org Cc: Dmitry Torokhov , Jaewon Kim , Chanwoo Choi , Kyungmin Park , Fabian Frederick , Axel Lin , linux-input@vger.kernel.org, Javier Martinez Canillas Subject: [PATCH v2 3/6] input: regulator-haptic: Fix module autoload for OF platform driver Message-ID: <20150829104726.GA20770@goodgumbo.baconseed.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1131 Lines: 34 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 --- Better without an empty line between of_device_id and MODULE_DEVICE_TABLE. Thanks, Luis drivers/input/misc/regulator-haptic.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/input/misc/regulator-haptic.c b/drivers/input/misc/regulator-haptic.c index 6bf3f10..a804705 100644 --- a/drivers/input/misc/regulator-haptic.c +++ b/drivers/input/misc/regulator-haptic.c @@ -249,6 +249,7 @@ static const struct of_device_id regulator_haptic_dt_match[] = { { .compatible = "regulator-haptic" }, { /* sentinel */ }, }; +MODULE_DEVICE_TABLE(of, regulator_haptic_dt_match); static struct platform_driver regulator_haptic_driver = { .probe = regulator_haptic_probe, -- 2.4.6 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/