From: Jenkins <jenkins@linuxtv.org>
To: mchehab+samsung@kernel.org, linux-media@vger.kernel.org
Cc: builder@linuxtv.org
Subject: Re: [GIT FIXES FOR v5.11] rc nsec to usec fix #2 (#70510)
Date: Wed, 6 Jan 2021 10:53:31 +0000 [thread overview]
Message-ID: <20210106105331.21808-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20210106104314.GA879@gofer.mess.org>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/project/linux-media/patch/20210106104314.GA879@gofer.mess.org/
Build log: https://builder.linuxtv.org/job/patchwork/84592/
Build time: 00:02:27
Link: https://lore.kernel.org/linux-media/20210106104314.GA879@gofer.mess.org
gpg: Signature made Wed 06 Jan 2021 10:13:08 AM UTC
gpg: using RSA key A624251A26084A9ED9E4C8B6425F639D3960FA9E
gpg: issuer "sean@mess.org"
gpg: Good signature from "Sean Young <sean@mess.org>" [full]
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:[~2021-01-06 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 10:43 [GIT FIXES FOR v5.11] rc nsec to usec fix #2 Sean Young
2021-01-06 10:53 ` 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=20210106105331.21808-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).