Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp5659393rwl; Tue, 11 Apr 2023 08:19:12 -0700 (PDT) X-Google-Smtp-Source: AKy350arRrSE18RS9TIXPBDHTdfZFjIkLRcRc6KAVRimw7DUG9wJy/aQ6bRnIYnQeUwmYbVeEMS6 X-Received: by 2002:a17:902:f1cb:b0:1a1:abcc:e44e with SMTP id e11-20020a170902f1cb00b001a1abcce44emr3294650plc.9.1681226352544; Tue, 11 Apr 2023 08:19:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681226352; cv=none; d=google.com; s=arc-20160816; b=Gu0wWtAgNHky3/uqQxJjX4y2T14Euu0wHx04H8nzHgnCM6Xb2227Wj2avcVE5YmuTy INLpQOLTUypU9IkjnrQkAgvoFfX2M4NDuku+6KI7RQHrxWYhrgpLRTUFhT6fRoVY9ivm 74rv2+/AyeBOea+wTIui2asWAX/X+iZcE0Hc2hDYH3sUeTTRsGNV0/dhbOGHwYI6EPEL NgPnEZaEbMNjyQl0GrDxl3zMlZFKtmd8EOdN0b1ANbDrKqtqk2rGoc7ll7EVMZZLm0pV Zei7J6rG4f5RADFp0xnetKB/uA9HhTkxSxS/zmRvz3N9nZcUy7ThNws6m8YcJNrT/Pqh A9gw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:feedback-id :dkim-signature:dkim-signature; bh=AA0MaJimcwNeJcPgKAoWqZxmdOXtBaxs17Z5PKlfdXE=; b=J4zaBCCWJpTj+sSUep4YahmXAPik+bu+L7kdVvgnjylqYuIO77WR1XRB9pMFQA7uYY 4fORpLYbjrPMuXxZavyLuH5dAFJR+jEv46IlXbCmEyHMf2y1FkH/n0e1pbbEjgGEDhFB 7itLvKnNTB7fECY53uTNb9DpHLbZQ9nNUiQ0BEeXvCBYgF0wMnRi4bpz0d0u8oBZKIae sofeCG+jbZpbJe8hL4nUds73qZ2IjanNdtOtXmTQq0On9V4l8zYSlefbGbpxug3jKFmA zwagmj7hk2miCUJeD7EbuUv3OpBjSbDEUl9oS4zQhp9QvwgQgO/q2MEwQaCMIuzHbKw/ Sdng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm3 header.b=Rk+OHcMZ; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=daUmgFHp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i10-20020a65484a000000b004fca80d4647si13473595pgs.216.2023.04.11.08.19.00; Tue, 11 Apr 2023 08:19:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm3 header.b=Rk+OHcMZ; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=daUmgFHp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231349AbjDKPRS (ORCPT + 99 others); Tue, 11 Apr 2023 11:17:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51406 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231355AbjDKPRF (ORCPT ); Tue, 11 Apr 2023 11:17:05 -0400 Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8E73A5FFB; Tue, 11 Apr 2023 08:16:32 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id EDFCC320029B; Tue, 11 Apr 2023 11:13:50 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 11 Apr 2023 11:13:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1681226030; x=1681312430; bh=AA 0MaJimcwNeJcPgKAoWqZxmdOXtBaxs17Z5PKlfdXE=; b=Rk+OHcMZD68dIIgyXJ b6/Fzs8Ppkw/v+ybMtbRyx/5c8gfReul4kc5Xtebcuj3U8i9GUNTlcWCWV+0HkF2 TFV9FybmFLht3VUfVqz3ahJzbfg0MePD0SR1MCeNGrf3h3jlctpIArs0mjQehplJ IHjw7Ox8s1phQIxfWrlifzG4v6qdzUUJL9/Lx+T+079w7enUTbKCPKSksy4HLa6m m27HHaB5OI7HRPZxLbFOCPPsa8zaSNI1hU6aQUiikI38M5cDbZWSDovzE6BIU09A xUJCY4hEmOpwAi3UGbAxMArL4P5Kkki+//X2YVUonAUYQ0XoS99U0WvrJQJWq/pI H8aw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1681226030; x=1681312430; bh=AA0MaJimcwNeJ cPgKAoWqZxmdOXtBaxs17Z5PKlfdXE=; b=daUmgFHp4e2eXr+3Z5LL9eTfPocST Q1Js6Xd5gwv1y/6H75G37B3oPXW15sSe96hzusFEr9fYqUrlVNEC9bxOEj+I7H7x GaI5Pw7DAsdG66HdwwPO/Fhmt1/frLGzQX8gMzE3SVVvS8fGiiUdksY28sWmOxe5 csjnk5RdI1J9a0Ci0rCFZXS9OPpjwnHfie7GQaatEW9Mhh+RGC8FYhIGh/bzrlEO ZemEmTtuawjB8+8gVfT0nHAvGPnmVKEB1N3yf9qUr0sZ6WTqE3lqqsYqZ3DvGt4V trAOOrMV+zhVWEbsN2SMNsH17Lcr7gT2STdByvYI22feRlN32Wb/Cqvvw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdekgedgkeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepheegvd evvdeljeeugfdtudduhfekledtiefhveejkeejuefhtdeufefhgfehkeetnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorg hhrdgtohhm X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 11 Apr 2023 11:13:49 -0400 (EDT) Date: Tue, 11 Apr 2023 17:13:47 +0200 From: Greg KH To: Jeffrey Hugo Cc: Oded Gabbay , Stephen Rothwell , Dave Airlie , Linux Kernel Mailing List , DRI , Pranjal Ramajor Asha Kanojiya , Linux Next Mailing List , Jacek Lawrynowicz Subject: Re: linux-next: build failure after merge of the driver-core tree Message-ID: <2023041131-boxy-excavator-1183@gregkh> References: <20230411143812.11a4b00d@canb.auug.org.au> <2023041123-tractor-quake-c44d@gregkh> <1094266f-d845-9fa4-9f44-85de8352c04f@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1094266f-d845-9fa4-9f44-85de8352c04f@quicinc.com> X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H2, SPF_HELO_PASS,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 11, 2023 at 09:08:39AM -0600, Jeffrey Hugo wrote: > On 4/11/2023 9:01 AM, Daniel Vetter wrote: > > On Tue, Apr 11, 2023 at 12:40:28PM +0200, Greg KH wrote: > > > On Tue, Apr 11, 2023 at 11:55:20AM +0200, Daniel Vetter wrote: > > > > On Tue, Apr 11, 2023 at 02:38:12PM +1000, Stephen Rothwell wrote: > > > > > Hi all, > > > > > > > > > > After merging the driver-core tree, today's linux-next build (x86_64 > > > > > allmodconfig) failed like this: > > > > > > > > > > In file included from include/linux/linkage.h:7, > > > > > from include/linux/kernel.h:17, > > > > > from drivers/accel/qaic/mhi_qaic_ctrl.c:4: > > > > > drivers/accel/qaic/mhi_qaic_ctrl.c: In function 'mhi_qaic_ctrl_init': > > > > > include/linux/export.h:27:22: error: passing argument 1 of 'class_create' from incompatible pointer type [-Werror=incompatible-pointer-types] > > > > > 27 | #define THIS_MODULE (&__this_module) > > > > > | ~^~~~~~~~~~~~~~~ > > > > > | | > > > > > | struct module * > > > > > drivers/accel/qaic/mhi_qaic_ctrl.c:544:38: note: in expansion of macro 'THIS_MODULE' > > > > > 544 | mqc_dev_class = class_create(THIS_MODULE, MHI_QAIC_CTRL_DRIVER_NAME); > > > > > | ^~~~~~~~~~~ > > > > > In file included from include/linux/device.h:31, > > > > > from include/linux/mhi.h:9, > > > > > from drivers/accel/qaic/mhi_qaic_ctrl.c:5: > > > > > include/linux/device/class.h:229:54: note: expected 'const char *' but argument is of type 'struct module *' > > > > > 229 | struct class * __must_check class_create(const char *name); > > > > > | ~~~~~~~~~~~~^~~~ > > > > > drivers/accel/qaic/mhi_qaic_ctrl.c:544:25: error: too many arguments to function 'class_create' > > > > > 544 | mqc_dev_class = class_create(THIS_MODULE, MHI_QAIC_CTRL_DRIVER_NAME); > > > > > | ^~~~~~~~~~~~ > > > > > include/linux/device/class.h:229:29: note: declared here > > > > > 229 | struct class * __must_check class_create(const char *name); > > > > > | ^~~~~~~~~~~~ > > > > > > > > > > Caused by commit > > > > > > > > > > 1aaba11da9aa ("driver core: class: remove module * from class_create()") > > > > > > > > > > interacting with commit > > > > > > > > > > 566fc96198b4 ("accel/qaic: Add mhi_qaic_cntl") > > > > > > > > > > from the drm tree. > > > > > > > > > > I have applied the following merge fix patch for today. > > > > > > > > > > From: Stephen Rothwell > > > > > Date: Tue, 11 Apr 2023 14:16:57 +1000 > > > > > Subject: [PATCH] fixup for "driver core: class: remove module * from class_create()" > > > > > > > > > > interacting with "accel/qaic: Add mhi_qaic_cntl" > > > > > > > > > > Signed-off-by: Stephen Rothwell > > > > > > > > Thanks for the fixup. Since Dave is out I've made a note about this in my > > > > handover mail so it won't get lost in the drm-next merge window pull. I > > > > don't think we need any other coordination than mention it in each pull to > > > > Linus, topic tree seems overkill for this. Plus there's no way I can > > > > untangle the drm tree anyway :-). > > > > > > Want me to submit a patch for the drm tree that moves this to use > > > class_register() instead, which will make the merge/build issue go away > > > for you? That's my long-term goal here anyway, so converting this new > > > code to this api today would be something I have to do eventually :) > > > > We kinda closed drm-next for feature work mostly already (just pulling > > stuff in from subtrees), so won't really help for this merge window. > > > > For everything else I think this is up to Oded, I had no idea qaic needed > > it's entire own dev class and I don't want to dig into this for the risk I > > might freak out :-) > > > > Adding Oded. > > > > Cheers, Daniel > > Sorry for the mess. > > I made a note to update to class_register() once my drm-misc access is > sorted out. Looks like we'll address the conflict in the merge window, and > catch the update to the new API in the following release. Wait, I think the large question is, "why does this need a separate class"? Why are you not using the accel char device and class? That is what everything under accel/ should be using, otherwise why put it in there? And what exactly are you using that class for? Just device nodes? If so, how many? thanks, greg k-h