From: Jonathan Cameron <jic23@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Mingjin Yang <mingjin.yang@unisoc.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
oe-kbuild-all@lists.linux.dev, magicyangmingjin@gmail.com,
Ling_Ling.Xu@unisoc.com, Jinfeng.Lin1@unisoc.com,
Yangbin.Li@unisoc.com, Jiansheng.Wu@unisoc.com,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V0 2/2] iio: adc: sprd_pmic_adc: Add support for UMP serise pmic adc
Date: Mon, 28 Aug 2023 15:38:21 +0100 [thread overview]
Message-ID: <20230828153821.51705a00@jic23-huawei> (raw)
In-Reply-To: <202308162143.UjXhwiRf-lkp@intel.com>
On Wed, 16 Aug 2023 22:07:15 +0800
kernel test robot <lkp@intel.com> wrote:
> Hi Mingjin,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on robh/for-next]
> [also build test WARNING on linus/master v6.5-rc6 next-20230816]
> [cannot apply to jic23-iio/togreg]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Mingjin-Yang/dt-bindings-iio-adc-Add-support-for-ump518-pmic-adc/20230816-160754
> base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
> patch link: https://lore.kernel.org/r/20230816080225.21482-3-mingjin.yang%40unisoc.com
> patch subject: [PATCH V0 2/2] iio: adc: sprd_pmic_adc: Add support for UMP serise pmic adc
> config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20230816/202308162143.UjXhwiRf-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230816/202308162143.UjXhwiRf-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/202308162143.UjXhwiRf-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> drivers/iio/adc/sprd_pmic_adc.c: In function 'ump9620_ch_data_init':
> >> drivers/iio/adc/sprd_pmic_adc.c:530:1: warning: the frame size of 1320 bytes is larger than 1024 bytes [-Wframe-larger-than=]
> 530 | }
> | ^
>
>
> vim +530 drivers/iio/adc/sprd_pmic_adc.c
>
> 506
> 507 static void ump9620_ch_data_init(struct sprd_adc_data *data)
> 508 {
> 509 struct sprd_adc_channel_data ch_data_def = CH_DATA_INIT(SCALE_00, 0, 0, RATIO_DEF);
> 510 struct sprd_adc_channel_data ch_data[SPRD_ADC_CHANNEL_MAX] = {
Make these both const and I think the compiler will move these off the stack thus
solving the issue seen.
> 511 [0] = CH_DATA_INIT(SCALE_01, 0, 0, RATIO_DEF),
> 512 [5] = CH_DATA_INIT(SCALE_00, 0x1, 0x9, RATIO_DEF),
> 513 [6] = CH_DATA_INIT(SCALE_00, 0x1, 0x9, RATIO_DEF),
> 514 [7] = CH_DATA_INIT(SCALE_10, 0, 0, RATIO_DEF),
> 515 [9] = CH_DATA_INIT(SCALE_10, 0, 0, RATIO_DEF),
> 516 [10] = CH_DATA_INIT(SCALE_11, 0, 0, RATIO_DEF),
> 517 [11] = CH_DATA_INIT(SCALE_00, 0, 0, RATIO_DEF),
> 518 [13] = CH_DATA_INIT(SCALE_01, 0, 0, RATIO_DEF),
> 519 [14] = CH_DATA_INIT(SCALE_00, 0, 0, RATIO(68, 900)),
> 520 [15] = CH_DATA_INIT(SCALE_00, 0, 0, RATIO(1, 3)),
> 521 [19] = CH_DATA_INIT(SCALE_11, 0, 0, RATIO_DEF),
> 522 [21] = CH_DATA_INIT(SCALE_00, 0, 0, RATIO(3, 8)),
> 523 [22] = CH_DATA_INIT(SCALE_00, 0, 0, RATIO(3, 8)),
> 524 [23] = CH_DATA_INIT(SCALE_00, 0, 0, RATIO(3, 8)),
> 525 [30] = CH_DATA_INIT(SCALE_11, 0, 0, RATIO_DEF),
> 526 [31] = CH_DATA_INIT(SCALE_11, 0, 0, RATIO_DEF),
> 527 };
> 528
> 529 sprd_adc_ch_data_merge(data, ch_data, &ch_data_def);
> > 530 }
> 531
>
next prev parent reply other threads:[~2023-08-28 14:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 8:02 [PATCH V0 0/2] Add support for UMP serise pmic adc Mingjin Yang
2023-08-16 8:02 ` [PATCH V0 1/2] dt-bindings: iio: adc: Add support for ump518 " Mingjin Yang
2023-08-16 14:44 ` Conor Dooley
2023-08-28 14:40 ` Jonathan Cameron
2023-08-16 8:02 ` [PATCH V0 2/2] iio: adc: sprd_pmic_adc: Add support for UMP serise " Mingjin Yang
2023-08-16 14:07 ` kernel test robot
2023-08-28 14:38 ` Jonathan Cameron [this message]
2023-08-28 15:57 ` Jonathan Cameron
2023-08-30 7:15 ` 杨明金
2023-09-03 11:14 ` Jonathan Cameron
2023-09-05 2:59 ` 杨明金
2023-09-10 13:57 ` Jonathan Cameron
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=20230828153821.51705a00@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jiansheng.Wu@unisoc.com \
--cc=Jinfeng.Lin1@unisoc.com \
--cc=Ling_Ling.Xu@unisoc.com \
--cc=Yangbin.Li@unisoc.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=magicyangmingjin@gmail.com \
--cc=mingjin.yang@unisoc.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=zhang.lyra@gmail.com \
/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).