From: Jenkins Builder Robot <jenkins@linuxtv.org>
To: mchehab@kernel.org, linux-media@vger.kernel.org
Subject: Jenkins build is back to normal : v4l-utils #45
Date: Wed, 2 Oct 2019 09:30:23 +0000 (UTC) [thread overview]
Message-ID: <838817409.3.1570008623849.JavaMail.jenkins@builder.linuxtv.org> (raw)
In-Reply-To: <786551029.2.1570006907525.JavaMail.jenkins@builder.linuxtv.org>
See <https://builder.linuxtv.org/job/v4l-utils/45/display/redirect>
prev parent reply other threads:[~2019-10-02 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 8:16 Build failed in Jenkins: v4l-utils #43 Jenkins Builder Robot
2019-10-02 8:25 ` Hans Verkuil
2019-10-02 9:36 ` Mauro Carvalho Chehab
2019-10-02 9:49 ` Hans Verkuil
2019-10-02 10:41 ` Mauro Carvalho Chehab
2019-10-02 10:56 ` Hans Verkuil
2019-10-02 9:01 ` Build failed in Jenkins: v4l-utils #44 Jenkins Builder Robot
2019-10-02 9:30 ` Jenkins Builder Robot [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=838817409.3.1570008623849.JavaMail.jenkins@builder.linuxtv.org \
--to=jenkins@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).