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.10] Miscellaneous UVC changes (#66842)
Date: Tue, 8 Sep 2020 19:58:00 +0000 [thread overview]
Message-ID: <20200908195800.31107-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20200908193533.GA9607@pendragon.ideasonboard.com>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/project/linux-media/patch/20200908193533.GA9607@pendragon.ideasonboard.com/
Build log: https://builder.linuxtv.org/job/patchwork/67471/
Build time: 00:16:30
Link: https://lore.kernel.org/linux-media/20200908193533.GA9607@pendragon.ideasonboard.com
gpg: Signature made Tue 08 Sep 2020 07:33:14 PM UTC
gpg: using RSA key BD94648A8E47ECEDBF199B1862255D299E280B24
gpg: issuer "laurent.pinchart@ideasonboard.com"
gpg: Good signature from "Laurent Pinchart <laurent.pinchart@ideasonboard.com>" [full]
Summary: got 1/10 patches with issues, being 1 at build time, plus one error when buinding PDF document
Error/warnings:
patches/0001-media-uvcvideo-Fix-annotation-for-uvc_video_clock_up.patch:
allyesconfig: return code #0:
../drivers/staging/media/atomisp/pci/atomisp_compat_css20.c: ../drivers/staging/media/atomisp/pci/atomisp_compat_css20.c:703 is_pipe_valid_to_current_run_mode() warn: ignoring unreachable code.
../drivers/staging/media/atomisp/pci/sh_css.c:1685:16: warning: assignment left-hand side might be a candidate for a format attribute [-Wsuggest-attribute=format]
allyesconfig: return code #0:
../drivers/media/usb/em28xx/em28xx-video.c: ../drivers/media/usb/em28xx/em28xx-video.c:2841 em28xx_v4l2_init() parse error: turning off implications after 60 seconds
Error #512 when building PDF docs
prev parent reply other threads:[~2020-09-08 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 19:35 [GIT PULL FOR v5.10] Miscellaneous UVC changes Laurent Pinchart
2020-09-08 19:58 ` 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=20200908195800.31107-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.