[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201127101159.GA1074530@gmail.com>
Date: Fri, 27 Nov 2020 11:11:59 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the tip tree
* Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> kernel/smp.c: In function 'csd_lock_wait_getcpu':
> kernel/smp.c:133:13: error: 'call_single_data_t' {aka 'struct __call_single_data'} has no member named 'dst'
> 133 | return csd->dst; /* Other CSD_TYPE_ values might not have ->dst. */
> | ^~
>
> Caused by commit
>
> 545b8c8df41f ("smp: Cleanup smp_call_function*()")
Inded, I just (belatedly) noticed this semantic merge conflict with
upstream too, I resolved it in tip:sched/core and it should be all sorted
out by tomorrow's -next integration. Sorry about this!
Thanks,
Ingo
Powered by blists - more mailing lists