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.15] rkisp1 support for px30 (#76158)
Date: Thu, 5 Aug 2021 14:07:50 +0000 [thread overview]
Message-ID: <20210805140750.1165-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <55ef358a-1173-7b4c-a238-e74ee80d5459@xs4all.nl>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/project/linux-media/patch/55ef358a-1173-7b4c-a238-e74ee80d5459@xs4all.nl/
Build log: https://builder.linuxtv.org/job/patchwork/129674/
Build time: 00:17:57
Link: https://lore.kernel.org/linux-media/55ef358a-1173-7b4c-a238-e74ee80d5459@xs4all.nl
gpg: Signature made Wed 04 Aug 2021 01:26:38 PM UTC
gpg: using RSA key AAA7FFBA4D2D77EF4CAEA1421326E0CD23ABDCE5
gpg: Good signature from "Hans Verkuil <hverkuil-cisco@xs4all.nl>" [unknown]
gpg: aka "Hans Verkuil <hverkuil@xs4all.nl>" [unknown]
gpg: Note: This key has expired!
Primary key fingerprint: 052C DE7B C215 053B 689F 1BCA BD2D 6148 6614 3B4C
Subkey fingerprint: AAA7 FFBA 4D2D 77EF 4CAE A142 1326 E0CD 23AB DCE5
Summary: got 3/10 patches with issues, being 1 at build time
Error/warnings:
patches/0001-media-rockchip-rkisp1-remove-unused-irq-variable.patch:
allyesconfig: return code #0:
../scripts/genksyms/parse.y: warning: 9 shift/reduce conflicts [-Wconflicts-sr]
../scripts/genksyms/parse.y: warning: 5 reduce/reduce conflicts [-Wconflicts-rr]
allyesconfig: return code #0:
SPARSE:../drivers/media/cec/core/cec-core.c ../include/asm-generic/bitops/find.h:90:32: warning: shift count is negative (-192)
SPARSE:../drivers/media/mc/mc-devnode.c ../include/asm-generic/bitops/find.h:90:32: warning: shift count is negative (-192)
SPARSE:../drivers/media/v4l2-core/v4l2-dev.c ../include/asm-generic/bitops/find.h:132:46: warning: shift count is negative (-192)
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:268 v4l_print_fmtdesc() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:292 v4l_print_format() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:302 v4l_print_format() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:328 v4l_print_format() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:347 v4l_print_format() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:352 v4l_print_format() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:362 v4l_print_framebuffer() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:735 v4l_print_frmsizeenum() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:762 v4l_print_frmivalenum() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/v4l2-core/v4l2-ioctl.c: ../drivers/media/v4l2-core/v4l2-ioctl.c:1424 v4l_fill_fmtdesc() error: unrecognized %p extension '4', treated as normal %p
../drivers/media/rc/meson-ir-tx.c:22: warning: expecting prototype for meson(). Prototype was for DEVICE_NAME() instead
../drivers/media/test-drivers/vivid/vivid-core.c: ../drivers/media/test-drivers/vivid/vivid-core.c:1969 vivid_create_instance() parse error: turning off implications after 60 seconds
../drivers/media/usb/em28xx/em28xx-video.c: ../drivers/media/usb/em28xx/em28xx-video.c:2856 em28xx_v4l2_init() parse error: turning off implications after 60 seconds
patches/0007-media-rockchip-rkisp1-add-prefixes-for-v10-specific-.patch:
checkpatch.pl:
$ cat patches/0007-media-rockchip-rkisp1-add-prefixes-for-v10-specific-.patch | formail -c | ./scripts/checkpatch.pl --terse --mailback --no-summary --strict
-:314: CHECK: Alignment should match open parenthesis
patches/0008-media-rockchip-rkisp1-add-support-for-v12-isp-varian.patch:
checkpatch.pl:
$ cat patches/0008-media-rockchip-rkisp1-add-support-for-v12-isp-varian.patch | formail -c | ./scripts/checkpatch.pl --terse --mailback --no-summary --strict
-:24: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
-:135: CHECK: Lines should not end with a '('
-:141: CHECK: Lines should not end with a '('
-:147: CHECK: Lines should not end with a '('
-:153: CHECK: Lines should not end with a '('
-:201: CHECK: Lines should not end with a '('
-:319: CHECK: Alignment should match open parenthesis
-:402: CHECK: Lines should not end with a '('
-:408: CHECK: Alignment should match open parenthesis
-:412: CHECK: Alignment should match open parenthesis
-:581: WARNING: line length of 102 exceeds 100 columns
prev parent reply other threads:[~2021-08-05 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 13:28 [GIT PULL FOR v5.15] rkisp1 support for px30 Hans Verkuil
2021-08-05 14:07 ` 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=20210805140750.1165-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).