On Thu, Jun 17, 2021 at 5:54 PM Naresh Kamboju
[off-list ref] wrote:

On Thu, 17 Jun 2021 at 19:22, Matthew Wilcox [off-list ref] wrote:

quoted

On Thu, Jun 17, 2021 at 06:15:45PM +0530, Naresh Kamboju wrote:

quoted

On Thu, 17 Jun 2021 at 17:41, Naresh Kamboju [off-list ref] wrote:

quoted

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 [off-list ref]
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 ?

Linux Next is not anyhow different to any other repository that does
merges. It takes the origin/master (Linus') tree as the base.

-- 
With Best Regards,
Andy Shevchenko