From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936515AbcKNC4X (ORCPT ); Sun, 13 Nov 2016 21:56:23 -0500 Received: from mga02.intel.com ([134.134.136.20]:12649 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933796AbcKNC4T (ORCPT ); Sun, 13 Nov 2016 21:56:19 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,488,1473145200"; d="scan'208";a="1084758869" Date: Mon, 14 Nov 2016 08:35:41 +0530 From: Vinod Koul To: Javier Martinez Canillas Cc: linux-kernel@vger.kernel.org, Dan Williams , dmaengine@vger.kernel.org Subject: Re: [PATCH] dmaengine: fsl_raid: Fix module autoload Message-ID: <20161114030541.GI3000@localhost> References: <1476909154-6305-1-git-send-email-javier@osg.samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1476909154-6305-1-git-send-email-javier@osg.samsung.com> 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 On Wed, Oct 19, 2016 at 05:32:33PM -0300, 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/dma/fsl_raid.ko | grep alias > $ > > After this patch: > > $ modinfo drivers/dma/fsl_raid.ko | grep alias > alias: of:N*T*Cfsl,raideng-v1.0C* > alias: of:N*T*Cfsl,raideng-v1.0 Applied, thanks -- ~Vinod