Re: Build regressions/improvements in v5.18-rc1

2022-04-04 Thread Kalle Valo
Geert Uytterhoeven writes: > On Mon, Apr 4, 2022 at 8:39 PM Kalle Valo wrote: >> Geert Uytterhoeven writes: >> >> /kisskb/src/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c: >> >> error: case label does not reduce to an integer constant: => 3798:2, >> >> 3809:2 >> > >> > arm64-gcc5.4/a

Re: Build regressions/improvements in v5.18-rc1

2022-04-04 Thread Geert Uytterhoeven
Hi Kalle, On Mon, Apr 4, 2022 at 8:39 PM Kalle Valo wrote: > Geert Uytterhoeven writes: > >> /kisskb/src/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c: > >> error: case label does not reduce to an integer constant: => 3798:2, > >> 3809:2 > > > > arm64-gcc5.4/arm64-allmodconfig > > powe

Re: [PATCH 0/4] um: Assorted console related fixes

2022-04-04 Thread Richard Weinberger
Glenn, On Thu, Mar 10, 2022 at 7:22 PM Glenn Washburn wrote: > > On Wed, 9 Mar 2022 09:35:02 +0100 (CET) > Richard Weinberger wrote: > > > - Ursprüngliche Mail - > > >> This series fixes the console exit code to make sure UML > > >> undoes everything it changed on the host side. > > > >

Re: Build regressions/improvements in v5.18-rc1

2022-04-04 Thread Kalle Valo
Geert Uytterhoeven writes: >> /kisskb/src/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c: >> error: case label does not reduce to an integer constant: => 3798:2, >> 3809:2 > > arm64-gcc5.4/arm64-allmodconfig > powerpc-gcc5/powerpc-allmodconfig > powerpc-gcc5/ppc64_book3e_allmodconfig Af

Re: UML time-travel warning from __run_timers

2022-04-04 Thread Thomas Gleixner
On Mon, Apr 04 2022 at 10:37, Johannes Berg wrote: > On Mon, 2022-04-04 at 10:32 +0200, Thomas Gleixner wrote: >> --- a/kernel/time/timer.c >> +++ b/kernel/time/timer.c >> @@ -1724,9 +1724,8 @@ static inline void __run_timers(struct t >> /* >> * The only possible reason f

Re: Build regressions/improvements in v5.18-rc1

2022-04-04 Thread Dave Chinner
On Mon, Apr 04, 2022 at 10:16:08AM +0200, Geert Uytterhoeven wrote: > On Mon, 4 Apr 2022, Geert Uytterhoeven wrote: > > Below is the list of build error/warning regressions/improvements in > > v5.18-rc1[1] compared to v5.17[2]. > > > > Summarized: > > - build errors: +36/-15 > > - build warnings

Re: UML time-travel warning from __run_timers

2022-04-04 Thread Johannes Berg
On Mon, 2022-04-04 at 10:32 +0200, Thomas Gleixner wrote: > On Mon, Apr 04 2022 at 09:02, Johannes Berg wrote: > > On Sun, 2022-04-03 at 21:51 +0200, Thomas Gleixner wrote: > > > but that's fine and it is overwritten by every timer which is inserted > > > to expire before that. So that's not an iss

Re: UML time-travel warning from __run_timers

2022-04-04 Thread Thomas Gleixner
On Mon, Apr 04 2022 at 09:02, Johannes Berg wrote: > On Sun, 2022-04-03 at 21:51 +0200, Thomas Gleixner wrote: >> but that's fine and it is overwritten by every timer which is inserted >> to expire before that. So that's not an issue as the prandom timer is >> firing and rearmed. > > No, as I said

Re: Build regressions/improvements in v5.18-rc1

2022-04-04 Thread Geert Uytterhoeven
On Mon, 4 Apr 2022, Geert Uytterhoeven wrote: Below is the list of build error/warning regressions/improvements in v5.18-rc1[1] compared to v5.17[2]. Summarized: - build errors: +36/-15 - build warnings: +5/-38 Happy fixing! ;-) Thanks to the linux-next team for providing the build service.

Re: UML time-travel warning from __run_timers

2022-04-04 Thread Johannes Berg
On Sun, 2022-04-03 at 21:51 +0200, Thomas Gleixner wrote: > > > There was no timer. If there's ever a timer on this base (BASE_DEF) then > > this doesn't happen. > > You said: > > > > > init_timer_cpu(0) base 0 clk=0x8ad0, next_expiry=0x13fff8acf > > > > init_timer_cpu(0) base 1 clk=0x8a