From: Jenkins Builder Robot <jenkins@linuxtv.org>
To: mchehab@kernel.org, linux-media@vger.kernel.org,
libcamera-devel@lists.libcamera.org
Subject: Jenkins build is back to normal : libcamera #361
Date: Mon, 16 Nov 2020 05:55:14 +0000 (UTC) [thread overview]
Message-ID: <204421797.49.1605506114744@builder.linuxtv.org> (raw)
In-Reply-To: <1745598416.48.1605479283109@builder.linuxtv.org>
See <https://builder.linuxtv.org/job/libcamera/361/display/redirect>
prev parent reply other threads:[~2020-11-16 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 10:33 Build failed in Jenkins: libcamera #357 Jenkins Builder Robot
2020-11-13 9:03 ` Build failed in Jenkins: libcamera #358 Jenkins Builder Robot
2020-11-15 22:27 ` Build failed in Jenkins: libcamera #359 Jenkins Builder Robot
2020-11-15 22:28 ` Build failed in Jenkins: libcamera #360 Jenkins Builder Robot
2020-11-16 5:55 ` 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=204421797.49.1605506114744@builder.linuxtv.org \
--to=jenkins@linuxtv.org \
--cc=libcamera-devel@lists.libcamera.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).