From: Linus Walleij <linus.walleij@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
"kernelci.org bot" <bot@kernelci.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
guillaume.tucker@collabora.com,
Paul Parsons <lost.distance@yahoo.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Matt Hart <matthew.hart@linaro.org>,
Philipp Zabel <philipp.zabel@gmail.com>,
Kevin Hilman <khilman@baylibre.com>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Russell King <linux@armlinux.org.uk>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Daniel Mack <daniel@zonque.org>
Subject: Re: broonie-regulator/for-next boot bisection: v5.0-rc2-20-g61b67608c6b9 on meson8b-odroidc1
Date: Wed, 16 Jan 2019 09:25:28 +0100 [thread overview]
Message-ID: <CACRpkdZwuLwEfTd+PnjvCs_WrAQyEUzT+_ToUecHS3ufJhNkeQ@mail.gmail.com> (raw)
In-Reply-To: <20190114215926.GF11073@sirena.org.uk>
On Mon, Jan 14, 2019 at 10:59 PM Mark Brown <broonie@kernel.org> wrote:
> Linus, I'm going to revert this whole series - not sure what's gone
> wrong here but I guess we can test easily with kernelci which is good.
That's fine and I'm onto it, I am trying to create a mock system to test
the gpio-regulator so I have some confidence it's not breaking these
boards before submitting again.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-16 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 20:40 broonie-regulator/for-next boot bisection: v5.0-rc2-20-g61b67608c6b9 on meson8b-odroidc1 kernelci.org bot
2019-01-14 21:59 ` Mark Brown
2019-01-16 8:25 ` Linus Walleij [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=CACRpkdZwuLwEfTd+PnjvCs_WrAQyEUzT+_ToUecHS3ufJhNkeQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=haojian.zhuang@gmail.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lost.distance@yahoo.com \
--cc=matthew.hart@linaro.org \
--cc=philipp.zabel@gmail.com \
--cc=robert.jarzmik@free.fr \
--cc=tomeu.vizoso@collabora.com \
/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).