All of
 help / color / mirror / Atom feed
From: Jenkins <>
Subject: Re: [GIT PULL FOR v5.6] Various fixes
Date: Mon,  6 Jan 2020 13:54:28 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


Pull request:
Build log:
Build time: 00:13:30

gpg: Signature made Mon 06 Jan 2020 01:34:08 PM UTC
gpg:                using RSA key AAA7FFBA4D2D77EF4CAEA1421326E0CD23ABDCE5
gpg: Good signature from "Hans Verkuil <>" [unknown]
gpg:                 aka "Hans Verkuil <>" [full]

Summary: 2 patches and/or PDF generation with issues, being 0 at build time


Error #256 when running ./scripts/ --terse --mailback --no-summary --strict patches/0002-media-v4l2-Fix-fourcc-names-for-12b-and-14b-packed-b.patch:
$ ./scripts/ --terse --mailback --no-summary --strict patches/0002-media-v4l2-Fix-fourcc-names-for-12b-and-14b-packed-b.patch
patches/0002-media-v4l2-Fix-fourcc-names-for-12b-and-14b-packed-b.patch:6: WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)

Error #256 when running ./scripts/ --terse --mailback --no-summary --strict patches/0010-media-pci-bt8xx-convert-to-i2c_new_scanned_device.patch:
$ ./scripts/ --terse --mailback --no-summary --strict patches/0010-media-pci-bt8xx-convert-to-i2c_new_scanned_device.patch
patches/0010-media-pci-bt8xx-convert-to-i2c_new_scanned_device.patch:35: WARNING: line over 80 characters

  reply	other threads:[~2020-01-06 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 13:36 [GIT PULL FOR v5.6] Various fixes Hans Verkuil
2020-01-06 13:54 ` Jenkins [this message]
2020-01-10 14:53 Hans Verkuil
2020-01-10 15:03 ` Jenkins
2020-01-13 12:17 Hans Verkuil
2020-01-13 12:22 ` Jenkins
2020-01-16 13:52 Hans Verkuil
2020-01-16 14:21 ` Jenkins

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.