public inbox for oe-kbuild@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: drivers/staging/iio/frequency/ad9832.c:115:60: error: expected ',' or ';' before 'i'
Date: Sun, 12 Apr 2026 17:59:48 +0800	[thread overview]
Message-ID: <202604121725.ewvBjt5e-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "bisect to a FBC not belonging to original linux-review patches: branch: linux-review/Joshua-Crofts/iio-frequency-ad9832-remove-kernel-h-proxy-header/20260412-132456, commit: 1d815eeb63e9efc21b0e38b1ba5ab08cfb23bef1"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Joshua Crofts <joshua.crofts1@gmail.com>
CC: 0day robot <lkp@intel.com>

tree:   https://github.com/intel-lab-lkp/linux/commits/Joshua-Crofts/iio-frequency-ad9832-remove-kernel-h-proxy-header/20260412-132456
head:   1d815eeb63e9efc21b0e38b1ba5ab08cfb23bef1
commit: 1d815eeb63e9efc21b0e38b1ba5ab08cfb23bef1 iio: frequency: ad9832: simplify bitwise math
date:   5 hours ago
:::::: branch date: 5 hours ago
:::::: commit date: 5 hours ago
config: arm-randconfig-004-20260412 (https://download.01.org/0day-ci/archive/20260412/202604121725.ewvBjt5e-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260412/202604121725.ewvBjt5e-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/r/202604121725.ewvBjt5e-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/staging/iio/frequency/ad9832.c: In function 'ad9832_calc_freqreg':
>> drivers/staging/iio/frequency/ad9832.c:115:60: error: expected ',' or ';' before 'i'
     115 |         u64 freqreg = (u64)fout * BIT_ULL(AD9832_FREQ_BITS)i;
         |                                                            ^


vim +115 drivers/staging/iio/frequency/ad9832.c

d89aa24585a5e35 drivers/staging/iio/frequency/ad9832.c Narcisa Ana Maria Vasile 2017-02-27  112  
ea707584bac187c drivers/staging/iio/dds/ad9832.c       Michael Hennerich        2011-02-09  113  static unsigned long ad9832_calc_freqreg(unsigned long mclk, unsigned long fout)
ea707584bac187c drivers/staging/iio/dds/ad9832.c       Michael Hennerich        2011-02-09  114  {
1d815eeb63e9efc drivers/staging/iio/frequency/ad9832.c Joshua Crofts            2026-04-11 @115  	u64 freqreg = (u64)fout * BIT_ULL(AD9832_FREQ_BITS)i;
1d815eeb63e9efc drivers/staging/iio/frequency/ad9832.c Joshua Crofts            2026-04-11  116  
ea707584bac187c drivers/staging/iio/dds/ad9832.c       Michael Hennerich        2011-02-09  117  	do_div(freqreg, mclk);
ea707584bac187c drivers/staging/iio/dds/ad9832.c       Michael Hennerich        2011-02-09  118  	return freqreg;
ea707584bac187c drivers/staging/iio/dds/ad9832.c       Michael Hennerich        2011-02-09  119  }
ea707584bac187c drivers/staging/iio/dds/ad9832.c       Michael Hennerich        2011-02-09  120  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-04-12 10:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202604121725.ewvBjt5e-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox