From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
lkft-triage@lists.linaro.org,
open list <linux-kernel@vger.kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Stephen Boyd <swboyd@chromium.org>, Jiri Olsa <jolsa@kernel.org>,
Alexei Starovoitov <ast@kernel.org>, Jessica Yu <jeyu@kernel.org>,
Evan Green <evgreen@chromium.org>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Baoquan He <bhe@redhat.com>, Borislav Petkov <bp@alien8.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Dave Young <dyoung@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
Sasha Levin <sashal@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vivek Goyal <vgoyal@redhat.com>, Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
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'
Date: Thu, 17 Jun 2021 18:13:42 +0300 [thread overview]
Message-ID: <CAHp75Vc05a3fpB+-xUjpeo+yeUuF-i4YUgZqzraURDgGmWs06A@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYukjZU9_88KuhW5FpG-Y6EOH4ehXgdKm9pGO0v4y4wsmA@mail.gmail.com>
On Thu, Jun 17, 2021 at 5:54 PM Naresh Kamboju
<naresh.kamboju@linaro.org> wrote:
> 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 ?
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
next prev parent reply other threads:[~2021-06-17 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 12:11 [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' Naresh Kamboju
2021-06-17 12:45 ` Naresh Kamboju
2021-06-17 13:51 ` Matthew Wilcox
2021-06-17 14:45 ` Naresh Kamboju
2021-06-17 15:07 ` Steven Rostedt
2021-06-17 15:13 ` Andy Shevchenko [this message]
2021-06-17 18:02 ` Nathan Chancellor
2021-06-18 5:02 ` Aneesh Kumar K.V
2021-06-18 23:05 ` Nathan Chancellor
2021-06-23 23:39 ` Nick Desaulniers
2021-06-24 0:18 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHp75Vc05a3fpB+-xUjpeo+yeUuF-i4YUgZqzraURDgGmWs06A@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=ast@kernel.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dyoung@redhat.com \
--cc=evgreen@chromium.org \
--cc=hsinyi@chromium.org \
--cc=jeyu@kernel.org \
--cc=jolsa@kernel.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lkft-triage@lists.linaro.org \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).