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.6] uvcvideo changes
Date: Tue, 21 Jan 2020 19:32:32 +0000 [thread overview]
Message-ID: <20200121193232.17255-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20200121192713.GH5003@pendragon.ideasonboard.com>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/61242/
Build log: https://builder.linuxtv.org/job/patchwork/34673/
Build time: 00:02:24
Link: https://lore.kernel.org/linux-media/20200121192713.GH5003@pendragon.ideasonboard.com
gpg: Signature made Tue 21 Jan 2020 07:21:24 PM UTC
gpg: using RSA key BD94648A8E47ECEDBF199B1862255D299E280B24
gpg: issuer "laurent.pinchart@ideasonboard.com"
gpg: Good signature from "Laurent Pinchart <laurent.pinchart@ideasonboard.com>" [full]
Summary: 1 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/0001-media-uvcvideo-Avoid-cyclic-entity-chains-due-to-mal.patch:
$ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0001-media-uvcvideo-Avoid-cyclic-entity-chains-due-to-mal.patch
patches/0001-media-uvcvideo-Avoid-cyclic-entity-chains-due-to-mal.patch:13: WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
patches/0001-media-uvcvideo-Avoid-cyclic-entity-chains-due-to-mal.patch:91: WARNING: quoted string split across lines
patches/0001-media-uvcvideo-Avoid-cyclic-entity-chains-due-to-mal.patch:103: WARNING: quoted string split across lines
prev parent reply other threads:[~2020-01-21 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 19:27 [GIT PULL FOR v5.6] uvcvideo changes Laurent Pinchart
2020-01-21 19:32 ` 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=20200121193232.17255-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