From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Andrea della Porta <andrea.porta@suse.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-clk@vger.kernel.org
Subject: Re: linux-next: Tree for Jun 3 (clk/clk-rp1.c)
Date: Thu, 5 Jun 2025 10:56:19 -0700 [thread overview]
Message-ID: <d642eba3-d7f2-4bf5-93ce-6ea491d4709a@broadcom.com> (raw)
In-Reply-To: <44c89b6b-edaa-4b0f-9306-a447ef2d9250@infradead.org>
On 6/5/25 10:07, Randy Dunlap wrote:
>
>
> On 6/5/25 6:52 AM, Andrea della Porta wrote:
>> On 20:06 Wed 04 Jun , Florian Fainelli wrote:
>>>
>>>
>>> On 6/3/2025 10:01 AM, Randy Dunlap wrote:
>>>>
>>>>
>>>> On 6/3/25 12:00 AM, Stephen Rothwell wrote:
>>>>> Hi all,
>>>>>
>>>>> Please do not add any material destined for v6.17 to you rlinux-next
>>>>> included branches until after v6.16-rc1 has been released.
>>>>>
>>>>> Changes since 20250530:
>>>>>
>>>>
>>>> on i386:
>>>>
>>>> ld: drivers/clk/clk-rp1.o: in function `rp1_pll_divider_set_rate':
>>>> clk-rp1.c:(.text+0xba1): undefined reference to `__udivdi3'
>>>>
>>>> caused by
>>>> /* must sleep 10 pll vco cycles */
>>>> ndelay(10ULL * div * NSEC_PER_SEC / parent_rate);
>>>>
>>>>
>>>
>>> Andrea, do you mind fixing this build error for a 32-bit kernel? Thanks!
>>
>> Sorry for the delay, this should fix it:
>>
>> @@ -754,7 +769,7 @@ static int rp1_pll_divider_set_rate(struct clk_hw *hw,
>> clockman_write(clockman, data->ctrl_reg, sec);
>>
>> /* must sleep 10 pll vco cycles */
>> - ndelay(10ULL * div * NSEC_PER_SEC / parent_rate);
>> + ndelay(div64_ul(10ULL * div * NSEC_PER_SEC, parent_rate));
>>
>> sec &= ~PLL_SEC_RST;
>> clockman_write(clockman, data->ctrl_reg, sec);
>>
>> should I send a new patch with this fix only (against linux-next or stblinux/next?)
>> or Florian is it better if you make the change in your next branch directly?
>
> Yes, this fixes the 32-bit build error. Thanks.
>
> Tested-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
>
Thank you both, amended the original commit with the change and added
Randy's tag.
--
Florian
prev parent reply other threads:[~2025-06-05 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 7:00 linux-next: Tree for Jun 3 Stephen Rothwell
2025-06-03 17:01 ` linux-next: Tree for Jun 3 (clk/clk-rp1.c) Randy Dunlap
2025-06-05 3:06 ` Florian Fainelli
2025-06-05 9:13 ` Andrea della Porta
2025-06-05 13:52 ` Andrea della Porta
2025-06-05 17:07 ` Randy Dunlap
2025-06-05 17:56 ` Florian Fainelli [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=d642eba3-d7f2-4bf5-93ce-6ea491d4709a@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrea.porta@suse.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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