From: Jenkins <jenkins@linuxtv.org>
To: mchehab+samsung@kernel.org, linux-media@vger.kernel.org
Cc: builder@linuxtv.org
Subject: Re: [GIT PULL v2 for 5.4] More sensor driver, omap3isp and documentation
Date: Wed, 14 Aug 2019 17:42:36 +0000 [thread overview]
Message-ID: <20190814174236.32180-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20190814103251.GA3504@valkosipuli.retiisi.org.uk>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/58128/
Build log: https://builder.linuxtv.org/job/patchwork/8689/
Build time: 00:08:45
Link: https://lore.kernel.org/linux-media/20190814103251.GA3504@valkosipuli.retiisi.org.uk
Summary: 3 issues, being 0 at build time
gpg: Signature made Wed 14 Aug 2019 10:10:12 AM UTC
gpg: using DSA key F0D0377A0D4F25A79238EFE56D40361B6E28C193
gpg: issuer "sakari.ailus@linux.intel.com"
gpg: Good signature from "Sakari Ailus <sakari.ailus@linux.intel.com>" [full]
Error/warnings:
patches/0001-ov5675-Add-support-for-OV5675-sensor.patch:660: CHECK: Alignment should match open parenthesis
patches/0001-ov5675-Add-support-for-OV5675-sensor.patch:709: CHECK: spaces preferred around that '/' (ctx:VxV)
patches/0001-ov5675-Add-support-for-OV5675-sensor.patch:774: CHECK: Alignment should match open parenthesis
patches/0001-ov5675-Add-support-for-OV5675-sensor.patch:781: CHECK: Alignment should match open parenthesis
patches/0001-ov5675-Add-support-for-OV5675-sensor.patch:786: CHECK: Alignment should match open parenthesis
patches/0001-ov5675-Add-support-for-OV5675-sensor.patch:791: CHECK: Alignment should match open parenthesis
Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0001-ov5675-Add-support-for-OV5675-sensor.patch
patches/0006-media-i2c-ov5645-Fix-power-sequence.patch:8: ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit aa4bb8b8838f ("media: ov5640: Re-work MIPI startup sequence")'
Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0006-media-i2c-ov5645-Fix-power-sequence.patch
patches/0008-v4l-Documentation-Raw-Bayer-formats-are-not-RGB-form.patch:53: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
patches/0008-v4l-Documentation-Raw-Bayer-formats-are-not-RGB-form.patch:58: WARNING: Missing or malformed SPDX-License-Identifier tag in line 1
Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0008-v4l-Documentation-Raw-Bayer-formats-are-not-RGB-form.patch
prev parent reply other threads:[~2019-08-14 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 10:32 [GIT PULL v2 for 5.4] More sensor driver, omap3isp and documentation patches Sakari Ailus
2019-08-14 12:08 ` [GIT PULL v2 for 5.4] More sensor driver, omap3isp and documentation Jenkins
2019-08-14 17:42 ` 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=20190814174236.32180-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).