linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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.5] am437x-vpfe: overdue maintenance
Date: Fri, 27 Sep 2019 14:44:05 +0000	[thread overview]
Message-ID: <20190927144405.17446-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <95a1c6a9-636f-66f4-0360-66105f22af57@xs4all.nl>

From: builder@linuxtv.org

Pull request: https://patchwork.linuxtv.org/patch/58971/
Build log: https://builder.linuxtv.org/job/patchwork/17976/
Build time: 00:13:55
Link: https://lore.kernel.org/linux-media/95a1c6a9-636f-66f4-0360-66105f22af57@xs4all.nl

gpg: Signature made Fri 27 Sep 2019 02:25:10 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>" [full]

Summary: 3 patches and/or PDF generation with issues, being 0 at build time

Error/warnings:

patches/0013-v4l-Add-macros-for-printing-V4L-fourcc-values.patch:70: ERROR: Macros with complex values should be enclosed in parentheses
patches/0013-v4l-Add-macros-for-printing-V4L-fourcc-values.patch:70: CHECK: Macro argument reuse 'fourcc' - possible side-effects?

Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0013-v4l-Add-macros-for-printing-V4L-fourcc-values.patch
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:24: WARNING: line over 80 characters
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:24: WARNING: Avoid logging continuation uses where feasible
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:39: WARNING: line over 80 characters
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:39: WARNING: Avoid logging continuation uses where feasible
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:54: WARNING: line over 80 characters
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:54: WARNING: Avoid logging continuation uses where feasible
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:73: WARNING: Avoid logging continuation uses where feasible
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:84: WARNING: Avoid logging continuation uses where feasible
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:102: WARNING: line over 80 characters
patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch:102: WARNING: Avoid logging continuation uses where feasible

Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0014-v4l2-ioctl.c-use-new-v4l2_fourcc_conv-args-macros.patch
patches/0015-media-am437x-vpfe-Remove-print_fourcc-helper.patch:76: WARNING: line over 80 characters
patches/0015-media-am437x-vpfe-Remove-print_fourcc-helper.patch:87: WARNING: line over 80 characters
patches/0015-media-am437x-vpfe-Remove-print_fourcc-helper.patch:98: WARNING: line over 80 characters
patches/0015-media-am437x-vpfe-Remove-print_fourcc-helper.patch:109: WARNING: line over 80 characters

Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0015-media-am437x-vpfe-Remove-print_fourcc-helper.patch


  reply	other threads:[~2019-09-27 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 14:27 [GIT PULL FOR v5.5] am437x-vpfe: overdue maintenance Hans Verkuil
2019-09-27 14:44 ` Jenkins [this message]
2019-10-01 19:33 ` Mauro Carvalho Chehab

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=20190927144405.17446-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).