[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75VcWamYQGg8dWdgTWV5ShV_DT9bfcv0b+WKyPHK7PsVS5w@mail.gmail.com>
Date: Mon, 10 Feb 2020 22:23:04 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Michal Simek <monstr@...str.eu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Michal Marek <michal.lkml@...kovi.net>
Subject: Re: [PATCH v1] kbuild: Fix off-by-one error when generate a new version
On Mon, Feb 10, 2020 at 10:15 PM Masahiro Yamada <masahiroy@...nel.org> wrote:
> On Mon, Jan 27, 2020 at 7:05 PM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> > On Fri, Jan 24, 2020 at 09:58:59PM +0200, Andy Shevchenko wrote:
...
> > > Additionally provide a unified way to get the current version of the build
> > > and use this in few callers. This will respect the KBUILD_BUILD_VERSION
> > > in case it's provided.
I still think there is second part in my patch to be considered, i.e. see above.
...
> I remember I was also hit by this one month ago or so.
>
> I did not dig into it at that time
> because the problem disappeared after doing something.
>
> Today, I took a look at this again.
> This is a regression caused by 56d589361572
>
> This patch should fix it:
> https://patchwork.kernel.org/patch/11374047/
Thank you.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists