From: Jenkins <jenkins@linuxtv.org>
To: Sean Young <sean@mess.org>,
mchehab+samsung@kernel.org, linux-media@vger.kernel.org
Cc: builder@linuxtv.org
Subject: Re: [GIT PULL FOR v5.4] RC & DVB
Date: Wed, 14 Aug 2019 07:47:42 +0000 [thread overview]
Message-ID: <20190814074742.4235-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20190814073135.avafdlmfjml3cqqs@gofer.mess.org>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/58121/
Build log: https://builder.linuxtv.org/job/patchwork/8398/
Build time: 00:14:29
Link: https://lore.kernel.org/linux-media/20190814073135.avafdlmfjml3cqqs@gofer.mess.orgSummary: 1 issues, being 0 at build time
Error/warnings:
patches/0013-media-tm6000-double-free-if-usb-disconnect-while-str.patch:30: WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0013-media-tm6000-double-free-if-usb-disconnect-while-str.patch
prev parent reply other threads:[~2019-08-14 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 7:31 [GIT PULL FOR v5.4] RC & DVB Sean Young
2019-08-14 7:47 ` 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=20190814074742.4235-1-jenkins@linuxtv.org \
--to=jenkins@linuxtv.org \
--cc=builder@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=sean@mess.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).