From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: can I trigger the 0day roboot "privately"?
Date: Tue, 19 Nov 2019 07:24:24 +0800 [thread overview]
Message-ID: <20191118232424.GA28652@intel.com> (raw)
In-Reply-To: <9e9694e7e232e78203f5a26912773cb2dd32e4cc.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Mon, Nov 18, 2019 at 05:19:38PM +0100, Paolo Abeni wrote:
> Hi all,
>
> I sometimes stumble upon build failures on submitted patches for
> uncommon build configurations. I'm wondering if there is a way to
> trigger the 0day robot - at least the build part - on a patch (series)
> _prior_ to submission to a public ML.
>
> That could possibly avoid some noise on the mentioned ML, and make
> submaintaiers more happy ;)
Hi Paolo, you can prepare a public accessible repo, and share us the url
such as github. We can monitor it to test.
>
> Thank you for any feedback,
>
> Paolo
> _______________________________________________
> LKP mailing list -- lkp(a)lists.01.org
> To unsubscribe send an email to lkp-leave(a)lists.01.org
prev parent reply other threads:[~2019-11-18 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 16:19 can I trigger the 0day roboot "privately"? Paolo Abeni
2019-11-18 23:24 ` Philip Li [this message]
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=20191118232424.GA28652@intel.com \
--to=philip.li@intel.com \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.