linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/fixes boot: 51 boots: 0 failed, 51 passed (v5.4)
Date: Mon, 25 Nov 2019 04:31:28 -0800 (PST)	[thread overview]
Message-ID: <5ddbc9a0.1c69fb81.75e0f.b3ba@mx.google.com> (raw)

linusw/fixes boot: 51 boots: 0 failed, 51 passed (v5.4)

Full Boot Summary: https://kernelci.org/boot/all/job/linusw/branch/fixes/kernel/v5.4/
Full Build Summary: https://kernelci.org/build/linusw/branch/fixes/kernel/v5.4/

Tree: linusw
Branch: fixes
Git Describe: v5.4
Git Commit: 219d54332a09e8d8741c1e1982f5eae56099de85
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Tested: 41 unique boards, 14 SoC families, 3 builds out of 6

---
For more info write to <info@kernelci.org>

                 reply	other threads:[~2019-11-25 12:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5ddbc9a0.1c69fb81.75e0f.b3ba@mx.google.com \
    --to=bot@kernelci.org \
    --cc=fellows@kernelci.org \
    --cc=linux-gpio@vger.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).