From: Michael Walle <michael@walle.cc>
To: Saravana Kannan <saravanak@google.com>
Cc: Mark Brown <broonie@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Ulf Hansson <ulf.hansson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernelci-results@groups.io, bot@kernelci.org,
gtucker@collabora.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
Heiko Thiery <heiko.thiery@gmail.com>
Subject: Re: next/master bisection: baseline.bootrr.imx6q-pcie-pcie0-probed on kontron-pitx-imx8m
Date: Mon, 04 Jul 2022 14:58:54 +0200 [thread overview]
Message-ID: <de79bf0e80138d91a5df5fe4a323e508@walle.cc> (raw)
In-Reply-To: <CAGETcx-ToG1xAtKVuZqwQK7hvVbT+Q0J0m4oWVCtR55XiYqETQ@mail.gmail.com>
[+ Heiko]
Am 2022-07-02 00:28, schrieb Saravana Kannan:
> On Fri, Jul 1, 2022 at 2:16 AM Mark Brown <broonie@kernel.org> wrote:
>>
>> On Thu, Jun 30, 2022 at 06:02:04PM -0700, Saravana Kannan wrote:
>>
>> > The patch attached to that email will probably fix this issue. I
>> > haven't dealt with Kernel CI bot before. Is there a way to get it to
>> > test a patch?
>>
>> It is but I don't have access to do that - either the lab owner
>> (Michael, CCed here) or Guillaume (also CCed) should be able to help
>> there.
>
> I found a much simpler solution that I think should work. Snippet at
> the end of this email.
> https://lore.kernel.org/lkml/CAGETcx-fLAXnG+1S4MHJwg9t7O6jj6Mp+q25bh==C_Z1CLs-mg@mail.gmail.com/
>
> I'm waiting for Alexander in that thread to give it a shot.
>
> Michael/Guillaume, if you want to give it a shot too, that'll be nice
> :)
Heiko will give it a try on his kontron-pitx-imx8m board.
-michael
prev parent reply other threads:[~2022-07-04 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62bdec26.1c69fb81.46bc5.2d67@mx.google.com>
2022-06-30 18:44 ` next/master bisection: baseline.bootrr.imx6q-pcie-pcie0-probed on kontron-pitx-imx8m Mark Brown
2022-06-30 21:48 ` Saravana Kannan
2022-07-01 1:02 ` Saravana Kannan
2022-07-01 9:16 ` Mark Brown
2022-07-01 22:28 ` Saravana Kannan
2022-07-01 22:34 ` Michael Walle
2022-07-04 12:58 ` Michael Walle [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=de79bf0e80138d91a5df5fe4a323e508@walle.cc \
--to=michael@walle.cc \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=gtucker@collabora.com \
--cc=heiko.thiery@gmail.com \
--cc=kernelci-results@groups.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=saravanak@google.com \
--cc=ulf.hansson@linaro.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