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.11-rc7] media fixes (#71221)
Date: Mon, 1 Feb 2021 16:25:04 +0000 [thread overview]
Message-ID: <20210201162504.7222-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20210201165609.21443571@coco.lan>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/project/linux-media/patch/20210201165609.21443571@coco.lan/
Build log: https://builder.linuxtv.org/job/patchwork/88358/
Build time: 00:09:08
Link: https://lore.kernel.org/linux-media/20210201165609.21443571@coco.lan
gpg: Signature made Mon 01 Feb 2021 03:52:16 PM 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/6 patches with issues, being 0 at build time, plus one error when buinding PDF document
Error/warnings:
patches/0006-media-rockchip-rkisp1-extend-uapi-array-sizes.patch:
checkpatch.pl:
$ cat patches/0006-media-rockchip-rkisp1-extend-uapi-array-sizes.patch | formail -c | ./scripts/checkpatch.pl --terse --mailback --no-summary --strict
-:109: WARNING: line length of 101 exceeds 100 columns
Error #512 when building PDF docs
next prev parent reply other threads:[~2021-02-01 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 15:56 [GIT PULL for v5.11-rc7] media fixes Mauro Carvalho Chehab
2021-02-01 16:25 ` Jenkins [this message]
2021-02-01 19:25 ` 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=20210201162504.7222-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.