From: Jenkins <jenkins@linuxtv.org>
To: mchehab+samsung@kernel.org, linux-media@vger.kernel.org
Cc: builder@linuxtv.org
Subject: Re: [GIT PULL for 5.11] One more fix for this cycle (#69887)
Date: Tue, 8 Dec 2020 12:49:50 +0000 [thread overview]
Message-ID: <20201208124950.24549-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20201208122543.GA1167@valkosipuli.retiisi.org.uk>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/project/linux-media/patch/20201208122543.GA1167@valkosipuli.retiisi.org.uk/
Build log: https://builder.linuxtv.org/job/patchwork/80429/
Build time: 00:04:29
Link: https://lore.kernel.org/linux-media/20201208122543.GA1167@valkosipuli.retiisi.org.uk
gpg: Signature made Mon 07 Dec 2020 08:30:48 PM UTC
gpg: using DSA key 53AC58A5F5948636C04A1BF8141DFA54A1EC8DEA
gpg: issuer "sakari.ailus@linux.intel.com"
gpg: Can't check signature: No public key
Summary: got 0/1 patches with issues, being 0 at build time, plus one error when buinding PDF document
Error/warnings:
Error #512 when building PDF docs
prev parent reply other threads:[~2020-12-08 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 12:25 [GIT PULL for 5.11] One more fix for this cycle Sakari Ailus
2020-12-08 12:49 ` Jenkins [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=20201208124950.24549-1-jenkins@linuxtv.org \
--to=jenkins@linuxtv.org \
--cc=builder@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@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).