linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: kbuild test robot <lkp@intel.com>
Cc: <kbuild-all@01.org>, <broonie@kernel.org>, <lgirdwood@gmail.com>,
	<linux-kernel@vger.kernel.org>, Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH] regulator: pwm: Try to avoid voltage error in duty cycle calculation
Date: Fri, 1 Apr 2016 12:02:19 +0530	[thread overview]
Message-ID: <56FE15F3.3060805@nvidia.com> (raw)
In-Reply-To: <201604011425.40GkbuYp%fengguang.wu@intel.com>


On Friday 01 April 2016 11:55 AM, kbuild test robot wrote:
> Hi Laxman,
>
> [auto build test ERROR on regulator/for-next]
> [also build test ERROR on v4.6-rc1 next-20160401]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url:    https://github.com/0day-ci/linux/commits/Laxman-Dewangan/regulator-pwm-Try-to-avoid-voltage-error-in-duty-cycle-calculation/20160331-220703
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
> config: i386-randconfig-a0-04010940 (attached as .config)
> reproduce:
>          # save the attached .config to linux build tree
>          make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
>     drivers/built-in.o: In function `pwm_regulator_set_voltage':
>>> pwm-regulator.c:(.text+0x1728d4): undefined reference to `__umoddi3'
>>> pwm-regulator.c:(.text+0x1728fd): undefined reference to `__udivdi3'
>


Seems build error is coming from logic

u64 req_period
unsigned int diff;
unsigned int period
unsigned int req_diff


req_period = req_diff * period;
if (req_period % diff == 0)


used u64 to avoid overflow in multiplication.

  reply	other threads:[~2016-04-01  6:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31 13:52 [PATCH] regulator: pwm: Try to avoid voltage error in duty cycle calculation Laxman Dewangan
2016-04-01  6:13 ` kbuild test robot
2016-04-01  6:25 ` kbuild test robot
2016-04-01  6:32   ` Laxman Dewangan [this message]
2016-04-02 16:53     ` Mark Brown
2016-04-03 11:07       ` Laxman Dewangan
2016-04-04 16:25         ` Mark Brown

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=56FE15F3.3060805@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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).