[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1809290835240.1432@nanos.tec.linutronix.de>
Date: Sat, 29 Sep 2018 08:38:55 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: kbuild test robot <lkp@...el.com>
cc: Julia Cartwright <julia@...com>, kbuild-all@...org,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rt-users@...r.kernel.org" <linux-rt-users@...r.kernel.org>,
Steffen Trumtrar <s.trumtrar@...gutronix.de>,
Tim Sander <tim@...eglstein.org>,
Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH RT 2/2] watchdog, rt: prevent deferral of watchdogd
wakeup
On Sat, 29 Sep 2018, kbuild test robot wrote:
> [also build test ERROR on v4.19-rc5 next-20180928]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
It's against the RT tree, so it won't work against next or upstream. I
think it would be good to have a machine parseable tag to describe which
tree/branch/commit patches are applicable to. If that tag is missing, the
bot can assume it's against upstream/next.
Thanks,
tglx
Powered by blists - more mailing lists