Linux-Media Archive on lore.kernel.org
 help / color / Atom feed
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] Various fixes
Date: Sun, 10 Nov 2019 11:36:26 +0000
Message-ID: <20191110113626.9277-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <06580f57-7b93-3bfd-7fa5-ad25732f3606@xs4all.nl>

From: builder@linuxtv.org

Pull request: https://patchwork.linuxtv.org/patch/59987/
Build log: https://builder.linuxtv.org/job/patchwork/24264/
Build time: 00:06:06
Link: https://lore.kernel.org/linux-media/06580f57-7b93-3bfd-7fa5-ad25732f3606@xs4all.nl

gpg: Signature made Sun 10 Nov 2019 11:20:01 AM UTC
gpg:                using RSA key AAA7FFBA4D2D77EF4CAEA1421326E0CD23ABDCE5
gpg: Good signature from "Hans Verkuil <hverkuil-cisco@xs4all.nl>" [unknown]
gpg:                 aka "Hans Verkuil <hverkuil@xs4all.nl>" [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-media-hantro-Fix-s_fmt-for-dynamic-resolution-change.patch:
$ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0003-media-hantro-Fix-s_fmt-for-dynamic-resolution-change.patch
patches/0003-media-hantro-Fix-s_fmt-for-dynamic-resolution-change.patch:6: WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
patches/0003-media-hantro-Fix-s_fmt-for-dynamic-resolution-change.patch:60: CHECK: Alignment should match open parenthesis

Error #256 when running ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0008-media-hantro-Fix-H264-motion-vector-buffer-offset.patch:
$ ./scripts/checkpatch.pl --terse --mailback --no-summary --strict patches/0008-media-hantro-Fix-H264-motion-vector-buffer-offset.patch
patches/0008-media-hantro-Fix-H264-motion-vector-buffer-offset.patch:18: WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)


      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 11:21 Hans Verkuil
2019-11-10 11:36 ` Jenkins [this message]

Reply instructions:

You may reply publically 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=20191110113626.9277-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

Linux-Media Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-media/0 linux-media/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-media linux-media/ https://lore.kernel.org/linux-media \
		linux-media@vger.kernel.org
	public-inbox-index linux-media

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-media


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git