From: kernel test robot <lkp@intel.com>
To: Jinseob Kim <kimjinseob88@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Subject: [jic23-iio:testing 55/58] drivers/iio/sensorhubs/osf/osf_core.c:17:6: warning: stack frame size (1344) exceeds limit (1280) in 'osf_core_init'
Date: Mon, 19 Oct 2026 15:37:22 +0800 [thread overview]
Message-ID: <202610191514.fRYyu0HX-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git testing
head: 43ffda3c7f8456bbe641ae8249a077a361b97880
commit: 2da37c28edc66848f7ff302011b765ae66ee8cf2 [55/58] iio: osf: add IIO devices from capability reports
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20261019/202610191514.fRYyu0HX-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 6719b9e31d6a93099612c474eec76d9f41d0275a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261019/202610191514.fRYyu0HX-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202610191514.fRYyu0HX-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/iio/sensorhubs/osf/osf_core.c:17:6: warning: stack frame size (1344) exceeds limit (1280) in 'osf_core_init' [-Wframe-larger-than]
17 | void osf_core_init(struct osf_device *osf, struct device *dev)
| ^
1 warning generated.
vim +/osf_core_init +17 drivers/iio/sensorhubs/osf/osf_core.c
33efb787fb5f8c Jinseob Kim 2026-10-12 16
33efb787fb5f8c Jinseob Kim 2026-10-12 @17 void osf_core_init(struct osf_device *osf, struct device *dev)
33efb787fb5f8c Jinseob Kim 2026-10-12 18 {
33efb787fb5f8c Jinseob Kim 2026-10-12 19 *osf = (struct osf_device) {
33efb787fb5f8c Jinseob Kim 2026-10-12 20 .dev = dev,
33efb787fb5f8c Jinseob Kim 2026-10-12 21 };
2da37c28edc668 Jinseob Kim 2026-10-12 22 mutex_init(&osf->latest_lock);
2da37c28edc668 Jinseob Kim 2026-10-12 23 }
2da37c28edc668 Jinseob Kim 2026-10-12 24
:::::: The code at line 17 was first introduced by commit
:::::: 33efb787fb5f8cc2053b241375a97c219b399aa3 iio: osf: add UART transport and core receive path
:::::: TO: Jinseob Kim <kimjinseob88@gmail.com>
:::::: CC: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-10-19 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 7:37 kernel test robot [this message]
2026-10-19 9:58 ` [PATCH] iio: osf: avoid a large stack frame in osf_core_init Jinseob Kim
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=202610191514.fRYyu0HX-lkp@intel.com \
--to=lkp@intel.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=kimjinseob88@gmail.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.