From: Igor Matheus Andrade Torrente <igormtorrente@gmail.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Melissa Wen <melissa.srw@gmail.com>
Cc: Haneen Mohammed <hamohammed.sa@gmail.com>,
Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>,
David Airlie <airlied@linux.ie>,
linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: build failure of next-20220906 due to 396369d67549 ("drm: vkms: Add support to the RGB565 format")
Date: Tue, 6 Sep 2022 20:35:49 -0300 [thread overview]
Message-ID: <8e4350df-0c73-6ca2-a25f-28a40a1856db@gmail.com> (raw)
In-Reply-To: <CADVatmNfc1YT02v5-FaMoGN==MOx5ZJ=o8YMQAH19Gvf91betA@mail.gmail.com>
On 9/6/22 18:26, Sudip Mukherjee wrote:
> On Tue, Sep 6, 2022 at 4:59 PM Sudip Mukherjee (Codethink)
> <sudipm.mukherjee@gmail.com> wrote:
>>
>> Hi All,
>>
>> The builds of next-20220906 fails for mips, xtensa and arm allmodconfig.
>>
>> The errors in mips and xtensa are:
>>
>> ERROR: modpost: "__divdi3" [drivers/gpu/drm/vkms/vkms.ko] undefined!
>> ERROR: modpost: "__udivdi3" [drivers/gpu/drm/vkms/vkms.ko] undefined!
>>
>> The error in arm is:
>>
>> ERROR: modpost: "__aeabi_uldivmod" [drivers/gpu/drm/vkms/vkms.ko] undefined!
>> ERROR: modpost: "__aeabi_ldivmod" [drivers/gpu/drm/vkms/vkms.ko] undefined!
>>
>>
>> Trying to do a git bisect to find out the offending commit.
>
> git bisect points to 396369d67549 ("drm: vkms: Add support to the
> RGB565 format")
Are these architectures incapable of doing 64bits int division?
>
>
next prev parent reply other threads:[~2022-09-06 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 15:59 build failure of next-20220906 for vkms Sudip Mukherjee (Codethink)
2022-09-06 21:26 ` build failure of next-20220906 due to 396369d67549 ("drm: vkms: Add support to the RGB565 format") Sudip Mukherjee
2022-09-06 23:35 ` Igor Matheus Andrade Torrente [this message]
2022-09-07 5:47 ` Daniel Vetter
2022-09-07 5:50 ` Daniel Vetter
2022-09-07 17:04 ` Melissa Wen
2022-09-07 18:34 ` Sudip Mukherjee
2022-09-07 19:22 ` Melissa Wen
2022-09-07 20:07 ` Sudip Mukherjee
2022-09-09 11:43 ` Melissa Wen
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=8e4350df-0c73-6ca2-a25f-28a40a1856db@gmail.com \
--to=igormtorrente@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=melissa.srw@gmail.com \
--cc=rodrigosiqueiramelo@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).