public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kernel test robot <lkp@intel.com>, x86-ml <x86@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [tip:tip] BUILD SUCCESS 3a1176a9af5a1b7d7a0a40b0975412008eb221c3
Date: Tue, 15 Jun 2021 10:55:03 +0800	[thread overview]
Message-ID: <20210615025503.GA507303@pl-dbox> (raw)
In-Reply-To: <YMPMFUsmj0F8btKc@zn.tnic>

On Fri, Jun 11, 2021 at 10:48:21PM +0200, Borislav Petkov wrote:
> On Sat, Jun 12, 2021 at 04:27:15AM +0800, kernel test robot wrote:
> > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tip
> > branch HEAD: 3a1176a9af5a1b7d7a0a40b0975412008eb221c3  auto-x86-next: Rename x86/seves to x86/sev
> 
> 0day folks:
> 
> if you have a way to exclude the 0day bot from testing some branches,
> this branch is one of them as it doesn't get code but only tip internal
> tracking changes and thus doesn't need to get tested by you so that you
> can save some infra for the real branches.
Got it, Boris, we will disable the testing of this tip branch, any branch
else that you think we can ignore?

So far, the configuration is below

branch_denylist: auto-.*|tmp-.*|base-.*|test.*|.*-for-linus|tip

Thanks

> 
> Thx.
> 
> -- 
> Regards/Gruss,
>     Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2021-06-15  3:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 20:27 [tip:tip] BUILD SUCCESS 3a1176a9af5a1b7d7a0a40b0975412008eb221c3 kernel test robot
2021-06-11 20:48 ` Borislav Petkov
2021-06-15  2:55   ` Philip Li [this message]
2021-06-15 13:04     ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210615025503.GA507303@pl-dbox \
    --to=philip.li@intel.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox