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] RC fixes (#66382)
Date: Thu, 27 Aug 2020 15:20:50 +0000 [thread overview]
Message-ID: <20200827152050.21807-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <20200819064442.GB25827@gofer.mess.org>
From: builder@linuxtv.org
Pull request: https://patchwork.linuxtv.org/project/linux-media/patch/20200819064442.GB25827@gofer.mess.org/
Build log: https://builder.linuxtv.org/job/patchwork/65989/
Build time: 00:02:38
Link: https://lore.kernel.org/linux-media/20200819064442.GB25827@gofer.mess.org
gpg: Signature made Wed 19 Aug 2020 06:29:45 AM UTC
gpg: using RSA key A624251A26084A9ED9E4C8B6425F639D3960FA9E
gpg: issuer "sean@mess.org"
gpg: Good signature from "Sean Young <sean@mess.org>" [full]
Summary: 1 patches and/or PDF generation with issues, being 0 at build time
prev parent reply other threads:[~2020-08-27 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 6:44 [GIT PULL FOR v5.10] RC fixes Sean Young
2020-08-19 7:16 ` [GIT PULL FOR v5.10] RC fixes (#20200819064442) Jenkins
2020-08-24 22:01 ` Jenkins
2020-08-27 15:20 ` 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=20200827152050.21807-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.