From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3B2CBC7EE29 for ; Tue, 6 Jun 2023 12:35:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237462AbjFFMfl (ORCPT ); Tue, 6 Jun 2023 08:35:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36030 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229835AbjFFMfi (ORCPT ); Tue, 6 Jun 2023 08:35:38 -0400 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C77FD10CA for ; Tue, 6 Jun 2023 05:35:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1686054937; x=1717590937; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=tA7wwf/t/7qt0yTKz623VV7kJiNe41UtCjTEvJ+qhiQ=; b=Bmm2wDpxx1QM+Fzvvzf9kFAj36oo2rqdi8If4hN1oFRvBguPh9xxkyX+ QpHFHhai4BmpHLhXbfyRql7YZG9NyRy83Pb2p17YEUqzVmd9hPcpr+tBZ VRoykhAes+/ANe+c7ppRj37yWKR7RN52kLwA8ztOsH5PrM0TiQ8lL9a4V VBungVwlsAvAN4rvNFtPmIyESxjqwCwbtQkf/OchORkoBVZgLSaXw6zJr jH3oVVfxVSRw0gnfwDcA//Sf8wMDljRt42ROMJ/QlKDKXjrQ/aYjE1HFn mF2ez/pBXQNnsAevDy6Kwp7jrctluNM/jfqULouvbjdtO+TsCbKjabbYP g==; X-IronPort-AV: E=McAfee;i="6600,9927,10732"; a="346254611" X-IronPort-AV: E=Sophos;i="6.00,221,1681196400"; d="scan'208";a="346254611" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jun 2023 05:35:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10732"; a="833208288" X-IronPort-AV: E=Sophos;i="6.00,221,1681196400"; d="scan'208";a="833208288" Received: from joe-255.igk.intel.com (HELO localhost) ([10.91.220.57]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jun 2023 05:35:33 -0700 Date: Tue, 6 Jun 2023 14:35:32 +0200 From: Stanislaw Gruszka To: Randy Dunlap Cc: linux-kernel@vger.kernel.org, kernel test robot , Oded Gabbay , dri-devel@lists.freedesktop.org, Jacek Lawrynowicz , Andrzej Kacprowski , Krystian Pradzynski , Jeffrey Hugo , Daniel Vetter Subject: Re: [PATCH] accel/ivpu: ivpu_ipc needs GENERIC_ALLOCATOR Message-ID: <20230606123532.GA324119@linux.intel.com> References: <20230526044519.13441-1-rdunlap@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230526044519.13441-1-rdunlap@infradead.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 25, 2023 at 09:45:19PM -0700, Randy Dunlap wrote: > Drivers that use the gen_pool*() family of functions should > select GENERIC_ALLOCATOR to prevent build errors like these: > > ld: drivers/accel/ivpu/ivpu_ipc.o: in function `gen_pool_free': > include/linux/genalloc.h:172: undefined reference to `gen_pool_free_owner' > ld: drivers/accel/ivpu/ivpu_ipc.o: in function `gen_pool_alloc_algo': > include/linux/genalloc.h:138: undefined reference to `gen_pool_alloc_algo_owner' > ld: drivers/accel/ivpu/ivpu_ipc.o: in function `gen_pool_free': > include/linux/genalloc.h:172: undefined reference to `gen_pool_free_owner' > ld: drivers/accel/ivpu/ivpu_ipc.o: in function `ivpu_ipc_init': > drivers/accel/ivpu/ivpu_ipc.c:441: undefined reference to `devm_gen_pool_create' > ld: drivers/accel/ivpu/ivpu_ipc.o: in function `gen_pool_add_virt': > include/linux/genalloc.h:104: undefined reference to `gen_pool_add_owner' > > Fixes: 5d7422cfb498 ("accel/ivpu: Add IPC driver and JSM messages") > Signed-off-by: Randy Dunlap > Reported-by: kernel test robot > Link: https://lore.kernel.org/all/202305221206.1TaugDKP-lkp@intel.com/ > Cc: Oded Gabbay > Cc: dri-devel@lists.freedesktop.org > Cc: Jacek Lawrynowicz > Cc: Stanislaw Gruszka > Cc: Andrzej Kacprowski > Cc: Krystian Pradzynski > Cc: Jeffrey Hugo > Cc: Daniel Vetter Applied to drm-misc-fixes Thanks Stanislaw