From: Diederik de Haas <didi.debian@cknow.org>
To: linux-rt-users@vger.kernel.org
Cc: didi.debian@cknow.org
Subject: Re: Build failure with 6.9-rt5 on arm64; works on amd64 and 6.9-rc6 on arm64
Date: Mon, 20 May 2024 00:28:43 +0200 [thread overview]
Message-ID: <5880304.cvb1nHMhLa@bagend> (raw)
In-Reply-To: <131999629.KQPSlr0Zke@bagend>
[-- Attachment #1: Type: text/plain, Size: 2719 bytes --]
On Friday, 17 May 2024 15:08:36 CEST Diederik de Haas wrote:
> In file included from
> /home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/in
> clude/linux/rwsem.h:15, from
> /home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/in
> clude/linux/notifier.h:15, from
> /home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/in
> clude/linux/clk.h:14, from
> /home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/dr
> ivers/pinctrl/renesas/pinctrl-rzg2l.c:10:
> /home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/dr
> ivers/pinctrl/renesas/pinctrl-rzg2l.c: In function ‘rzg2l_gpio_irq_restore’:
> /home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/dr
> ivers/pinctrl/renesas/pinctrl-rzg2l.c:2072:52: error: ‘spinlock_t’ {aka
> ‘struct spinlock’} has no member named ‘rlock’; did you mean ‘lock’? 2072 |
> raw_spin_lock_irqsave(&pctrl->lock.rlock, flags);
> | ^~~~~
>
> /home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/inc
> lude/linux/spinlock.h:244:48: note: in definition of macro
> ‘raw_spin_lock_irqsave’ 244 | flags =
> _raw_spin_lock_irqsave(lock); \
>
> | ^~~~
>
> /home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/dri
> vers/pinctrl/renesas/pinctrl-rzg2l.c:2076:57: error: ‘spinlock_t’ {aka
> ‘struct spinlock’} has no member named ‘rlock’; did you mean ‘lock’? 2076 |
> raw_spin_unlock_irqrestore(&pctrl->lock.rlock, flags);
> | ^~~~~
>
> /home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/inc
> lude/linux/spinlock.h:282:45: note: in definition of macro
> ‘raw_spin_unlock_irqrestore’ 282 |
> _raw_spin_unlock_irqrestore(lock, flags); \
> | ^~~~
>
> make[8]: ***
> [/home/diederik/dev/debian/salsa/kernel-team/linux/debian/build/source_rt/s
> cripts/Makefile.build:249: drivers/pinctrl/renesas/pinctrl-rzg2l.o] Error 1
https://salsa.debian.org/kernel-team/linux/-/merge_requests/1081#note_492742
pointed me to the following 2 commits which got added in 6.9-rc7:
https://git.kernel.org/linus/aa43c15a790cf083a6e6a7c531cffd27a5e1fd4f
https://git.kernel.org/linus/02cd2d3be1c31a3fd328ee83e576340d34bc57d9
I'm inclined to think those are very relevant, but I don't know enough
about this material to be sure.
Cheers,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-05-19 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 13:08 Build failure with 6.9-rt5 on arm64; works on amd64 and 6.9-rc6 on arm64 Diederik de Haas
2024-05-19 22:28 ` Diederik de Haas [this message]
2024-05-20 5:48 ` Mike Galbraith
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=5880304.cvb1nHMhLa@bagend \
--to=didi.debian@cknow.org \
--cc=linux-rt-users@vger.kernel.org \
/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