From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: Jenkins Builder Robot <jenkins@linuxtv.org>,
linux-media@vger.kernel.org,
LibCamera Devel <libcamera-devel@lists.libcamera.org>
Subject: Re: Build failed in Jenkins: libcamera #72
Date: Tue, 21 Jan 2020 14:14:14 +0100 [thread overview]
Message-ID: <20200121141414.7f8e9c89@kernel.org> (raw)
In-Reply-To: <263aa6e2-9b6c-5939-687d-005ae8fc2059@ideasonboard.com>
Em Sun, 19 Jan 2020 21:16:31 +0000
Kieran Bingham <kieran.bingham@ideasonboard.com> escreveu:
> Hi Mauro,
>
> As a side note, is it possible (or desirable?) to cc
> <libcamera-devel@lists.libcamera.org> on these failures to make sure we
> see them?
Added.
Cheers,
Mauro
prev parent reply other threads:[~2020-01-21 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 0:03 Build failed in Jenkins: libcamera #72 Jenkins Builder Robot
2020-01-16 17:48 ` Build failed in Jenkins: libcamera #73 Jenkins Builder Robot
2020-01-16 23:33 ` Build failed in Jenkins: libcamera #74 Jenkins Builder Robot
2020-01-16 23:48 ` Build failed in Jenkins: libcamera #75 Jenkins Builder Robot
2020-01-18 20:48 ` Build failed in Jenkins: libcamera #76 Jenkins Builder Robot
2020-01-20 17:03 ` Build failed in Jenkins: libcamera #77 Jenkins Builder Robot
2020-01-21 13:26 ` Build failed in Jenkins: libcamera #78 Jenkins Builder Robot
2020-01-21 13:38 ` Jenkins build is back to normal : libcamera #79 Jenkins Builder Robot
2020-01-19 21:16 ` Build failed in Jenkins: libcamera #72 Kieran Bingham
2020-01-21 13:12 ` Mauro Carvalho Chehab
2020-01-21 13:46 ` Mauro Carvalho Chehab
2020-01-21 13:48 ` Kieran Bingham
2020-01-21 13:47 ` Kieran Bingham
2020-01-21 14:22 ` Mauro Carvalho Chehab
2020-01-21 13:51 ` [libcamera-devel] " Laurent Pinchart
2020-01-21 13:54 ` Laurent Pinchart
2020-01-21 14:28 ` Mauro Carvalho Chehab
2020-01-21 13:14 ` Mauro Carvalho Chehab [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=20200121141414.7f8e9c89@kernel.org \
--to=mchehab@kernel.org \
--cc=jenkins@linuxtv.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=libcamera-devel@lists.libcamera.org \
--cc=linux-media@vger.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