[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240814161606.1b514882@gandalf.local.home>
Date: Wed, 14 Aug 2024 16:16:06 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Kris Van Hees <kris.van.hees@...cle.com>
Cc: linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
linux-modules@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Nick
Alcock <nick.alcock@...cle.com>, Alan Maguire <alan.maguire@...cle.com>,
Masahiro Yamada <masahiroy@...nel.org>, Luis Chamberlain
<mcgrof@...nel.org>, Masami Hiramatsu <mhiramat@...nel.org>, Nick
Desaulniers <ndesaulniers@...gle.com>, Jiri Olsa <olsajiri@...il.com>,
Elena Zannoni <elena.zannoni@...cle.com>
Subject: Re: [PATCH v5 3/4] scripts: add verifier script for builtin module
range data
On Wed, 14 Aug 2024 15:59:58 -0400
Kris Van Hees <kris.van.hees@...cle.com> wrote:
> > What does this mean?
>
> Hm, this is certainly why the validation script exists. I am surprised, though
> not entirely because kernel changes toward the 6.10 branching and such came
> after I create this version. Would you be willing to send me a copy of your
> .config for this kernel build so I can investigate? This output is typical
> of a case where the script was not able to determine offse ranges correctly.
Attached.
-- Steve
Download attachment "config" of type "application/octet-stream" (166682 bytes)
Powered by blists - more mailing lists