From: Jenkins <jenkins@linuxtv.org>
To: mchehab+samsung@kernel.org, linux-media@vger.kernel.org
Cc: builder@linuxtv.org
Subject: Re: [GIT PULL for 5.6] Sensor, V4L2 fwnode and ImgU driver patches
Date: Tue, 21 Jan 2020 16:57:56 +0000 [thread overview]
Message-ID: <20200121165756.23824-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20200121164816.GW856@valkosipuli.retiisi.org.uk>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/61240/
Build log: https://builder.linuxtv.org/job/patchwork/34657/
Build time: 00:07:46
Link: https://lore.kernel.org/linux-media/20200121164816.GW856@valkosipuli.retiisi.org.uk
gpg: Signature made Tue 21 Jan 2020 04:07:19 PM 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]
Summary: 2 patches and/or PDF generation with issues, being 0 at build time
Error/warnings:
Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0003-Revert-media-staging-intel-ipu3-make-imgu-use-fixed-.patch:
$ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0003-Revert-media-staging-intel-ipu3-make-imgu-use-fixed-.patch
patches/0003-Revert-media-staging-intel-ipu3-make-imgu-use-fixed-.patch:112: WARNING: line over 80 characters
Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0007-media-i2c-Add-driver-for-Sony-IMX219-sensor.patch:
$ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0007-media-i2c-Add-driver-for-Sony-IMX219-sensor.patch
patches/0007-media-i2c-Add-driver-for-Sony-IMX219-sensor.patch:60: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
next prev parent reply other threads:[~2020-01-21 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 16:48 [GIT PULL for 5.6] Sensor, V4L2 fwnode and ImgU driver patches Sakari Ailus
2020-01-21 16:57 ` Jenkins [this message]
2020-02-18 17:18 ` Helen Koike
2020-02-18 17:20 ` Sakari Ailus
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=20200121165756.23824-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).