Messages in this thread | | | From | Naresh Kamboju <> | Date | Thu, 17 Jun 2021 20:15:13 +0530 | Subject | Re: [next] [clang] x86_64-linux-gnu-ld: mm/mremap.o: in function `move_pgt_entry': mremap.c:(.text+0x763): undefined reference to `__compiletime_assert_342' |
| |
Hi Matthew,
On Thu, 17 Jun 2021 at 19:22, Matthew Wilcox <willy@infradead.org> wrote: > > On Thu, Jun 17, 2021 at 06:15:45PM +0530, Naresh Kamboju wrote: > > On Thu, 17 Jun 2021 at 17:41, Naresh Kamboju <naresh.kamboju@linaro.org> wrote: > > > x86_64-linux-gnu-ld: mm/mremap.o: in function `move_pgt_entry': > > > mremap.c:(.text+0x763): undefined reference to `__compiletime_assert_342' > > > > The git bisect pointed out the first bad commit. > > > > The first bad commit: > > commit 928cf6adc7d60c96eca760c05c1000cda061604e > > Author: Stephen Boyd <swboyd@chromium.org> > > Date: Thu Jun 17 15:21:35 2021 +1000 > > module: add printk formats to add module build ID to stacktraces > > Your git bisect probably went astray. There's no way that commit > caused that regression.
Sorry for pointing to incorrect bad commits coming from git bisect.
Any best way to run git bisect on linux next tree ?
Here is the git bisect log from gitlab pipeline, https://gitlab.com/Linaro/lkft/bisect/-/jobs/1354963448
- Naresh
| |