From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============1520890516956153314==" MIME-Version: 1.0 From: Christoph Hellwig To: kbuild-all@lists.01.org Subject: Re: drivers/of/unittest.c:910:1: warning: the frame size of 1424 bytes is larger than 1024 bytes Date: Fri, 19 Nov 2021 07:11:03 +0100 Message-ID: <20211119061103.GC15001@lst.de> In-Reply-To: <202111190545.G3a209mT-lkp@intel.com> List-Id: --===============1520890516956153314== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable I think we'll need to dynamically allocate the fake struct device here. Jim, can you look into that? --===============1520890516956153314==-- 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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 52924C433F5 for ; Fri, 19 Nov 2021 06:11:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 272C861B3D for ; Fri, 19 Nov 2021 06:11:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232107AbhKSGOJ (ORCPT ); Fri, 19 Nov 2021 01:14:09 -0500 Received: from verein.lst.de ([213.95.11.211]:49944 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229905AbhKSGOH (ORCPT ); Fri, 19 Nov 2021 01:14:07 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id B41E168AFE; Fri, 19 Nov 2021 07:11:03 +0100 (CET) Date: Fri, 19 Nov 2021 07:11:03 +0100 From: Christoph Hellwig To: kernel test robot Cc: Jim Quinlan , kbuild-all@lists.01.org, linux-kernel@vger.kernel.org, Christoph Hellwig , Mathieu Poirier Subject: Re: drivers/of/unittest.c:910:1: warning: the frame size of 1424 bytes is larger than 1024 bytes Message-ID: <20211119061103.GC15001@lst.de> References: <202111190545.G3a209mT-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202111190545.G3a209mT-lkp@intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I think we'll need to dynamically allocate the fake struct device here. Jim, can you look into that?