Messages in this thread | | | Date | Mon, 20 Jul 2020 15:37:06 +1000 | From | Stephen Rothwell <> | Subject | Re: linux-next: build failure after merge of the tip tree |
| |
Hi all,
On Tue, 14 Jul 2020 13:50:12 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > On Tue, 7 Jul 2020 12:33:01 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > On Tue, 30 Jun 2020 12:54:59 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > > > On Mon, 22 Jun 2020 11:37:00 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > > > failed like this: > > > > > > > > ERROR: modpost: "sched_setscheduler" [kernel/trace/ring_buffer_benchmark.ko] undefined! > > > > > > > > Caused by commit > > > > > > > > 616d91b68cd5 ("sched: Remove sched_setscheduler*() EXPORTs") > > > > > > > > Missed one :-) > > > > > > > > I have reverted that commit for today. > > > > > > I am still reverting that commit. > > > > Ditto ... > > Ping?
OK, it has now been three weeks ... I must admit I was a little suprised that initial testing of the tip tree (or even the branch that this commit is on) did not pick this up.
Unless there is something really weird going on here, Linus will notice if you try to get him to pull this as he tests with an x86_64 allmodconfig build.
-- Cheers, Stephen Rothwell [unhandled content-type:application/pgp-signature] | |