From: patchwork-bot+chrome-platform@kernel.org
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: bleung@chromium.org, groeck@chromium.org,
chrome-platform@lists.linux.dev, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev, lkp@intel.com
Subject: Re: [PATCH] platform/chrome: cros_ec_proto: remove big stub objects from stack
Date: Wed, 18 Jan 2023 06:20:16 +0000 [thread overview]
Message-ID: <167402281631.11174.10502033632687140262.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230117080254.2725536-1-tzungbi@kernel.org>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Tue, 17 Jan 2023 16:02:54 +0800 you wrote:
> sizeof(struct device) = 680
> sizeof(struct cros_ec_dev) = 720
>
> They tend to exceed the stack frame size limit in some specific
> environment which results in the following compilation error:
>
> >> drivers/platform/chrome/cros_ec_proto_test.c:2530:13: error: stack
> frame size (2128) exceeds limit (2048) in
> 'cros_ec_proto_test_get_sensor_count_legacy'
>
> [...]
Here is the summary with links:
- platform/chrome: cros_ec_proto: remove big stub objects from stack
https://git.kernel.org/chrome-platform/c/6514bac4a321
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-01-18 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 8:02 [PATCH] platform/chrome: cros_ec_proto: remove big stub objects from stack Tzung-Bi Shih
2023-01-17 16:24 ` Guenter Roeck
2023-01-18 3:00 ` patchwork-bot+chrome-platform
2023-01-18 6:20 ` patchwork-bot+chrome-platform [this message]
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=167402281631.11174.10502033632687140262.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzungbi@kernel.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