[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <831EE4E5E37DCC428EB295A351E662494CD1CCC3@shsmsx102.ccr.corp.intel.com>
Date: Sun, 30 Sep 2018 01:41:18 +0000
From: "Li, Philip" <philip.li@...el.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Thomas Gleixner <tglx@...utronix.de>
CC: "linux-rt-users@...r.kernel.org" <linux-rt-users@...r.kernel.org>,
"Julia Cartwright" <julia@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kbuild-all@...org" <kbuild-all@...org>,
"Tim Sander" <tim@...eglstein.org>,
Steffen Trumtrar <s.trumtrar@...gutronix.de>,
Guenter Roeck <linux@...ck-us.net>, lkp <lkp@...el.com>
Subject: RE: [kbuild-all] [PATCH RT 2/2] watchdog, rt: prevent deferral of
watchdogd wakeup
> Subject: Re: [kbuild-all] [PATCH RT 2/2] watchdog, rt: prevent deferral of
> watchdogd wakeup
>
> On 2018-09-29 08:38:55 [+0200], Thomas Gleixner wrote:
> > 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.
>
> I asked the testing team to ignore patches or test against the RT tree
> if the patch is tagged [PATCH RT]. I think it worked since I haven't
> seen those mails.
thanks Sebastian for the input, we will consider this to add to our TODO.
>
> > Thanks,
> >
> > tglx
>
> Sebastian
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@...ts.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
Powered by blists - more mailing lists