linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: Jenkins <jenkins@linuxtv.org>,
	mchehab+samsung@kernel.org, linux-media@vger.kernel.org
Cc: builder@linuxtv.org
Subject: Re: [GIT PULL for v5.6] Venus updates
Date: Wed, 15 Jan 2020 14:58:02 +0200	[thread overview]
Message-ID: <0e7e8329-15b4-cee6-16cd-ce0dec9e600a@linaro.org> (raw)
In-Reply-To: <20200110145511.8772-1-jenkins@linuxtv.org>

Hi Mauro,

On 1/10/20 4:55 PM, Jenkins wrote:
> From: builder@linuxtv.org
> 
> Pull request: https://patchwork.linuxtv.org/patch/61112/
> Build log: https://builder.linuxtv.org/job/patchwork/33062/
> Build time: 00:05:03
> Link: https://lore.kernel.org/linux-media/20200110144017.16648-1-stanimir.varbanov@linaro.org
> 
> gpg: Signature made Fri 10 Jan 2020 02:33:09 PM UTC
> gpg:                using RSA key E1558C2497CE3CCC2B5AA30F25B55FC81B7035F2
> gpg: Good signature from "Stanimir Varbanov <stanimir.varbanov@linaro.org>" [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:          There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 34CF E039 8A16 AD93 18FD  D5E8 A6D0 26D8 E358 14D4
>      Subkey fingerprint: E155 8C24 97CE 3CCC 2B5A  A30F 25B5 5FC8 1B70 35F2
> 
> Summary: 6 patches and/or PDF generation with issues, being 0 at build time
> 
> Error/warnings:
> 
> 

I'm not sure how to fix bellow warnings.

I found [1], which seems describe the issue.

[1] https://lore.kernel.org/patchwork/patch/527353/

> Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0003-venus-redesign-clocks-and-pm-domains-control.patch:
> $ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0003-venus-redesign-clocks-and-pm-domains-control.patch
> patches/0003-venus-redesign-clocks-and-pm-domains-control.patch:679: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> 
> Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0007-dt-bindings-media-venus-Convert-msm8916-to-DT-schema.patch:
> $ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0007-dt-bindings-media-venus-Convert-msm8916-to-DT-schema.patch
> patches/0007-dt-bindings-media-venus-Convert-msm8916-to-DT-schema.patch:16: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> 
> Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0008-dt-bindings-media-venus-Convert-msm8996-to-DT-schema.patch:
> $ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0008-dt-bindings-media-venus-Convert-msm8996-to-DT-schema.patch
> patches/0008-dt-bindings-media-venus-Convert-msm8996-to-DT-schema.patch:16: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> 
> Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0009-dt-bindings-media-venus-Convert-sdm845-to-DT-schema.patch:
> $ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0009-dt-bindings-media-venus-Convert-sdm845-to-DT-schema.patch
> patches/0009-dt-bindings-media-venus-Convert-sdm845-to-DT-schema.patch:16: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> 
> Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0010-dt-bindings-media-venus-Add-sdm845v2-DT-schema.patch:
> $ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0010-dt-bindings-media-venus-Add-sdm845v2-DT-schema.patch
> patches/0010-dt-bindings-media-venus-Add-sdm845v2-DT-schema.patch:16: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> 
> Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0012-dt-bindings-media-venus-delete-old-binding-document.patch:
> $ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0012-dt-bindings-media-venus-delete-old-binding-document.patch
> patches/0012-dt-bindings-media-venus-delete-old-binding-document.patch:17: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> patches/0012-dt-bindings-media-venus-delete-old-binding-document.patch:20: WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.txt
> 

-- 
regards,
Stan

  reply	other threads:[~2020-01-15 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 14:40 [GIT PULL for v5.6] Venus updates Stanimir Varbanov
2020-01-10 14:55 ` Jenkins
2020-01-15 12:58   ` Stanimir Varbanov [this message]
2020-02-13 10:58 ` Stanimir Varbanov

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=0e7e8329-15b4-cee6-16cd-ce0dec9e600a@linaro.org \
    --to=stanimir.varbanov@linaro.org \
    --cc=builder@linuxtv.org \
    --cc=jenkins@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).