From: Jenkins <jenkins@linuxtv.org>
To: mchehab+samsung@kernel.org, linux-media@vger.kernel.org
Cc: builder@linuxtv.org
Subject: Re: [GIT PULL for v5.10] media fixes (#69927)
Date: Thu, 10 Dec 2020 11:36:21 +0000 [thread overview]
Message-ID: <20201210113621.32036-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20201210121818.2d5c0353@coco.lan>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/project/linux-media/patch/20201210121818.2d5c0353@coco.lan/
Build log: https://builder.linuxtv.org/job/patchwork/80710/
Build time: 00:05:03
Link: https://lore.kernel.org/linux-media/20201210121818.2d5c0353@coco.lan
gpg: Signature made Thu 10 Dec 2020 11:10:56 AM UTC
gpg: using RSA key F909AE68FC11DF09C1755C00085F3EBD8EE4E115
gpg: Good signature from "Mauro Carvalho Chehab <mchehab+huawei@kernel.org>" [ultimate]
gpg: aka "Mauro Carvalho Chehab <mchehab@kernel.org>" [ultimate]
gpg: aka "Mauro Carvalho Chehab <m.chehab@samsung.com>" [ultimate]
gpg: aka "Mauro Carvalho Chehab <mchehab@osg.samsung.com>" [ultimate]
gpg: aka "Mauro Carvalho Chehab <mchehab@s-opensource.com>" [ultimate]
gpg: aka "Mauro Carvalho Chehab <mchehab+samsung@kernel.org>" [ultimate]
gpg: aka "[jpeg image of size 3594]" [ultimate]
Summary: got 1/7 patches with issues, being 0 at build time, plus one error when buinding PDF document
Error/warnings:
patches/0005-media-next-media-vidtv-fix-a-read-from-an-object-aft.patch:
checkpatch.pl:
$ cat patches/0005-media-next-media-vidtv-fix-a-read-from-an-object-aft.patch | formail -c | ./scripts/checkpatch.pl --terse --mailback --no-summary --strict
-:13: WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
Error #512 when building PDF docs
next prev parent reply other threads:[~2020-12-10 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 11:18 [GIT PULL for v5.10] media fixes Mauro Carvalho Chehab
2020-12-10 11:36 ` Jenkins [this message]
2020-12-10 19:12 ` pr-tracker-bot
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=20201210113621.32036-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).