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.4-rc1] media updates
Date: Mon, 16 Sep 2019 12:30:34 +0000 [thread overview]
Message-ID: <20190916123034.25744-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20190916092515.66549c3b@coco.lan>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/58782/
Build log: https://builder.linuxtv.org/job/patchwork/16380/
Build time: 00:00:00
Link: https://lore.kernel.org/linux-media/20190916092515.66549c3b@coco.lan
gpg: Signature made Mon 16 Sep 2019 12:06:35 PM UTC
gpg: using RSA key F909AE68FC11DF09C1755C00085F3EBD8EE4E115
gpg: Good signature from "Mauro Carvalho Chehab <mchehab+samsung@kernel.org>" [ultimate]
gpg: aka "Mauro Carvalho Chehab <mchehab@kernel.org>" [ultimate]
gpg: aka "Mauro Carvalho Chehab <m.chehab@samsung.com>" [ultimate]
gpg: aka "Mauro Carvalho Chehab <mchehab@osg.samsung.com>" [ultimate]
gpg: aka "Mauro Carvalho Chehab <mchehab@s-opensource.com>" [ultimate]
gpg: aka "[jpeg image of size 3594]" [ultimate]
Build aborted due to a fatal error:
FAILED: patch patch patches/0001-media-v4l2-ioctl-add-missing-pixelformats.patch doesn't apply:
Applying patch patches/0001-media-v4l2-ioctl-add-missing-pixelformats.patch
patching file drivers/media/v4l2-core/v4l2-ioctl.c
Hunk #1 FAILED at 1169.
Hunk #2 FAILED at 1186.
Hunk #3 FAILED at 1301.
Hunk #4 FAILED at 1326.
4 out of 4 hunks FAILED -- rejects in file drivers/media/v4l2-core/v4l2-ioctl.c
Patch patches/0001-media-v4l2-ioctl-add-missing-pixelformats.patch can be reverse-applied
next prev parent reply other threads:[~2019-09-16 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 12:25 [GIT PULL for v5.4-rc1] media updates Mauro Carvalho Chehab
2019-09-16 12:30 ` Jenkins [this message]
2019-09-18 2:15 ` pr-tracker-bot
2019-10-01 12:20 ` 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:
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=20190916123034.25744-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 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).