Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756427AbdCGWXE (ORCPT ); Tue, 7 Mar 2017 17:23:04 -0500 Received: from mail-wr0-f193.google.com ([209.85.128.193]:36749 "EHLO mail-wr0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751826AbdCGWWM (ORCPT ); Tue, 7 Mar 2017 17:22:12 -0500 Date: Tue, 7 Mar 2017 23:21:08 +0100 From: Daniel Vetter To: Noralf =?iso-8859-1?Q?Tr=F8nnes?= Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, thomas.petazzoni@free-electrons.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 1/7] drm: Add DRM support for tiny LCD displays Message-ID: <20170307222108.ofhnyrzs2bnbhqt5@phenom.ffwll.local> Mail-Followup-To: Noralf =?iso-8859-1?Q?Tr=F8nnes?= , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, thomas.petazzoni@free-electrons.com, linux-kernel@vger.kernel.org References: <20170211184858.26421-1-noralf@tronnes.org> <20170211184858.26421-2-noralf@tronnes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170211184858.26421-2-noralf@tronnes.org> X-Operating-System: Linux phenom 4.8.0-1-amd64 User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1001 Lines: 31 On Sat, Feb 11, 2017 at 07:48:52PM +0100, Noralf Tr?nnes wrote: > +const struct file_operations tinydrm_fops = { > + .owner = THIS_MODULE, > + .open = drm_open, > + .release = drm_release, > + .unlocked_ioctl = drm_ioctl, > +#ifdef CONFIG_COMPAT > + .compat_ioctl = drm_compat_ioctl, > +#endif > + .poll = drm_poll, > + .read = drm_read, > + .llseek = no_llseek, > + .mmap = drm_gem_cma_mmap, > +}; > +EXPORT_SYMBOL(tinydrm_fops); Just spotted this while doing a drive-by refactoring, this doesn't really work. The THIS_MODULE must be in the source code for your driver, and can't be in some helper library module like tinydrm.ko. I'm working on a macro to make this easier, and I guess you could try to integrate that into your driver macro somehow (probably simplest to generate the entire structure and just pass name+desc to that macro, everything else is boilerplate anyway). I'll cc you on that patch. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch