From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"kernelci-results@groups.io" <kernelci-results@groups.io>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Johan Hovold <johan@kernel.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Collabora Kernel ML <kernel@collabora.com>,
Sean Wang <sean.wang@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: linusw/devel bisection: baseline.bootrr.mediatek-mt8173-pinctrl-probed on mt8173-elm-hana
Date: Wed, 16 Dec 2020 17:30:43 +0000 [thread overview]
Message-ID: <600ff528-71b0-ac02-0266-ddc5e3b6fcf4@collabora.com> (raw)
In-Reply-To: <CACRpkdb8Bgie3dJME5qQwu_33b6zVYzAayJnHJUCzrkntpNNXw@mail.gmail.com>
On 16/12/2020 12:41, Linus Walleij wrote:
> On Wed, Dec 16, 2020 at 11:10 AM Guillaume Tucker
> <guillaume.tucker@collabora.com> wrote:
>
>>> It seems we need to teach the core to ignore the name (empty string).
>>
>> OK great, I see you've sent a patch for that. I'll check if we
>> can confirm it fixes the issue (something I'd like to also
>> automate...).
>
> Yups would love to hear if this solves it, it should be in today's
> -next.
Yes in fact it appears to be all fixed on your for-next branch:
https://kernelci.org/test/case/id/5fda32f92738afa48dc94ce1/
Today's linux-next was not tested in the Collabora lab because of
some infrastructure problem, but that's resolved now so it should
be in tomorrow's results.
Best wishes,
Guillaume
next prev parent reply other threads:[~2020-12-16 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5fd76cf2.1c69fb81.6f19b.b16a@mx.google.com>
2020-12-14 22:28 ` Guillaume Tucker
2020-12-15 12:20 ` Linus Walleij
2020-12-16 10:10 ` Guillaume Tucker
2020-12-16 12:41 ` Linus Walleij
2020-12-16 17:30 ` Guillaume Tucker [this message]
2020-12-16 20:52 ` Linus Walleij
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=600ff528-71b0-ac02-0266-ddc5e3b6fcf4@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=bgolaszewski@baylibre.com \
--cc=enric.balletbo@collabora.com \
--cc=geert+renesas@glider.be \
--cc=johan@kernel.org \
--cc=kernel@collabora.com \
--cc=kernelci-results@groups.io \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=sean.wang@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
all inboxes | Powered by JetHome®