linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <lkp@intel.com>
Cc: Jim Quinlan <james.quinlan@broadcom.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>,
	Mathieu Poirier <mathieu.poirier@linaro.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	[thread overview]
Message-ID: <20211119061103.GC15001@lst.de> (raw)
In-Reply-To: <202111190545.G3a209mT-lkp@intel.com>

I think we'll need to dynamically allocate the fake struct device here.
Jim, can you look into that?

  reply	other threads:[~2021-11-19  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 21:10 drivers/of/unittest.c:910:1: warning: the frame size of 1424 bytes is larger than 1024 bytes kernel test robot
2021-11-19  6:11 ` Christoph Hellwig [this message]
2021-11-19 14:29   ` Jim Quinlan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211119061103.GC15001@lst.de \
    --to=hch@lst.de \
    --cc=james.quinlan@broadcom.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mathieu.poirier@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).