[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1908300748100.1938@nanos.tec.linutronix.de>
Date: Fri, 30 Aug 2019 08:01:36 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: kbuild test robot <lkp@...el.com>
cc: tip-bot2 for Thomas Gleixner <tip-bot2@...utronix.de>,
kbuild-all@...org, linux-tip-commits@...r.kernel.org,
Frederic Weisbecker <frederic@...nel.org>,
Ingo Molnar <mingo@...nel.org>, Borislav Petkov <bp@...en8.de>,
LKML <linux-kernel@...r.kernel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [tip: timers/core] itimers: Use quick sample function
On Fri, 30 Aug 2019, kbuild test robot wrote:
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [cannot apply to v5.3-rc6 next-20190829]
Of course not. Because the patch is already in v5.3-rc6 next-20190829
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
I did so several times now and so did Borislav.
Can you please stop applying random patches from tip-bot2 notifications
which are part of a larger series and if applied alone obviously fail
because the prerequisite patches fail?
tip-bot2 mails are notifications that a patch has been merged into a branch
of the tip tree. They contain the information in which branch these patches
are applied so please start testing that branch in the proper order or
ignore tip-bot2 completely.
I really value your service, but recently the usefulness to noise ratio has
degraded massively.
Thanks,
tglx
Powered by blists - more mailing lists