From: Mark Brown <broonie@kernel.org>
To: Kevin Hilman <khilman@baylibre.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"kernelci.org bot" <bot@kernelci.org>,
Neil Armstrong <narmstrong@baylibre.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
guillaume.tucker@collabora.com,
Haojian Zhuang <haojian.zhuang@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Philipp Zabel <philipp.zabel@gmail.com>,
Paul Parsons <lost.distance@yahoo.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: broonie-regulator/for-next boot bisection: v5.0-rc2-20-g61b67608c6b9 on meson-gxl-s905x-libretech-cc
Date: Tue, 15 Jan 2019 18:56:18 +0000 [thread overview]
Message-ID: <20190115185618.GF5522@sirena.org.uk> (raw)
In-Reply-To: <7ha7k1ker7.fsf@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
On Tue, Jan 15, 2019 at 09:33:00AM -0800, Kevin Hilman wrote:
> Linus Walleij <linus.walleij@linaro.org> writes:
> > I hope there is someone else with this board on CC since I don't
> > know how to ask the robot to test patches.
> Both Neil and I have access to this board, so we can test any fixes for
> you.
Given the amount of work Linus is doing at the minute on GPIO API
cleanups that affect lots of boards I'm thinking it might be sensible
for him to have a tree in KernelCI where he can test things before
posting them upstream?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-01-15 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 22:04 broonie-regulator/for-next boot bisection: v5.0-rc2-20-g61b67608c6b9 on meson-gxl-s905x-libretech-cc kernelci.org bot
2019-01-15 11:38 ` Russell King - ARM Linux admin
2019-01-15 11:57 ` Guillaume Tucker
2019-01-15 12:53 ` Linus Walleij
2019-01-15 17:33 ` Kevin Hilman
2019-01-15 18:56 ` Mark Brown [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=20190115185618.GF5522@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bot@kernelci.org \
--cc=guillaume.tucker@collabora.com \
--cc=haojian.zhuang@gmail.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lost.distance@yahoo.com \
--cc=narmstrong@baylibre.com \
--cc=philipp.zabel@gmail.com \
--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