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] DVB/RC fixes (3nd)
Date: Fri, 8 Nov 2019 11:45:44 +0000 [thread overview]
Message-ID: <20191108114544.12374-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20191108112041.GA14408@gofer.mess.org>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/59959/
Build log: https://builder.linuxtv.org/job/patchwork/23976/
Build time: 00:15:31
Link: https://lore.kernel.org/linux-media/20191108112041.GA14408@gofer.mess.org
gpg: Signature made Fri 08 Nov 2019 09:11:23 AM UTC
gpg: using RSA key A624251A26084A9ED9E4C8B6425F639D3960FA9E
gpg: issuer "sean@mess.org"
gpg: Good signature from "Sean Young <sean@mess.org>" [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/0004-media-rc-add-keymap-for-Beelink-GS1-remote-control.patch:
$ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0004-media-rc-add-keymap-for-Beelink-GS1-remote-control.patch
patches/0004-media-rc-add-keymap-for-Beelink-GS1-remote-control.patch:33: WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.txt
patches/0004-media-rc-add-keymap-for-Beelink-GS1-remote-control.patch:46: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
patches/0004-media-rc-add-keymap-for-Beelink-GS1-remote-control.patch:52: WARNING: 'ment' may be misspelled - perhaps 'meant'?
patches/0004-media-rc-add-keymap-for-Beelink-GS1-remote-control.patch:134: WARNING: 'ment' may be misspelled - perhaps 'meant'?
prev parent reply other threads:[~2019-11-08 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 11:20 [GIT PULL FOR v5.5] DVB/RC fixes (3nd) Sean Young
2019-11-08 11:45 ` 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=20191108114544.12374-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.