From: "Farber, Eliav" <farbere@amazon.com>
To: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>,
Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
<linux-hwmon@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-next@vger.kernel.org>
Subject: Re: build failure of next-20220921 due to 94c025b6f735 ("hwmon: (mr75203) modify the temperature equation according to series 5 datasheet")
Date: Wed, 21 Sep 2022 15:19:41 +0300 [thread overview]
Message-ID: <04cb2084-7023-2a0b-ef31-ce25a54132cf@amazon.com> (raw)
In-Reply-To: <Yyr7c4IjjcnWZ3mr@debian>
On 9/21/2022 2:54 PM, Sudip Mukherjee (Codethink) wrote:
> Hi All,
>
> The builds of arm, mips and xtensa allmodconfig have failed to build
> next-20220921.
>
> Error from xtensa and mips build:
> ERROR: modpost: "__udivdi3" [drivers/hwmon/mr75203.ko] undefined!
> ERROR: modpost: "__divdi3" [drivers/hwmon/mr75203.ko] undefined!
>
> Error from arm build:
> ERROR: modpost: "__aeabi_uldivmod" [drivers/hwmon/mr75203.ko] undefined!
> ERROR: modpost: "__aeabi_ldivmod" [drivers/hwmon/mr75203.ko] undefined!
>
> git bisect pointed to 94c025b6f735 ("hwmon: (mr75203) modify the
> temperature equation according to series 5 datasheet")
>
> I will be happy to test any patch or provide any extra log if needed.
I just provided two potential fixes.
One is an incremental patch on top of the previous series of patches.
Second, I reworked it into the original series and modified two of the
patches.
You are recipient to both.
--
Regards, Eliav
prev parent reply other threads:[~2022-09-21 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 11:54 build failure of next-20220921 due to 94c025b6f735 ("hwmon: (mr75203) modify the temperature equation according to series 5 datasheet") Sudip Mukherjee (Codethink)
2022-09-21 12:19 ` Farber, Eliav [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=04cb2084-7023-2a0b-ef31-ce25a54132cf@amazon.com \
--to=farbere@amazon.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=p.zabel@pengutronix.de \
--cc=sudipm.mukherjee@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