From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Ulf Hansson <ulf.hansson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [next] arm: PM: domains: Delete usage of driver_deferred_probe_check_state()
Date: Thu, 28 Jul 2022 11:04:49 +0530 [thread overview]
Message-ID: <CA+G9fYv0DFZi2rMPQTHvK8yD7g0LZTxN76iKZxP4pi4+8Rstxg@mail.gmail.com> (raw)
In-Reply-To: <CAGETcx8bGwDkPP=d2MtcY69YmTyckUSa8xAwNVOPOyTR8jPk=A@mail.gmail.com>
Hi Saravana,
On Thu, 28 Jul 2022 at 00:19, Saravana Kannan <saravanak@google.com> wrote:
>
> On Tue, Jul 26, 2022 at 11:44 PM Naresh Kamboju
> <naresh.kamboju@linaro.org> wrote:
> >
> > Linux next arm BeagleBoard x15 device boot failed due to the
>
> Can you point me to the dts file that corresponds to this board
> please? And if you know which devices are power domains, that'd be
> handy too. For now, I'm reverting this patch.
metadata:
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_sha: 9250d2f72dc46a808b6aa23bf50dd670f1f52ddc
git_describe: v5.19-rc7-13490-g9250d2f72dc4
git_ref: master
kernel_version: 5.19.0-rc8
kernel-config: https://builds.tuxbuild.com/2CWh3jswUGEkjvfXQPGXdOceMFH/config
artifact-location: https://builds.tuxbuild.com/2CWh3jswUGEkjvfXQPGXdOceMFH
toolchain: gcc-10
I am sharing a few urls, metadata, test job link and device details link.
kernel:
url: https://builds.tuxbuild.com/2CWh3jswUGEkjvfXQPGXdOceMFH/zImage
dtb:
url: https://builds.tuxbuild.com/2CWh3jswUGEkjvfXQPGXdOceMFH/dtbs/am57xx-beagle-x15.dtb
modules:
url: https://builds.tuxbuild.com/2CWh3jswUGEkjvfXQPGXdOceMFH/modules.tar.xz
Test jobs url:
- https://lkft.validation.linaro.org/scheduler/job/5326314#L1982
Device details link,
- https://www.ti.com/tool/BEAGLEBOARD-X15
metadata:
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_sha: 9250d2f72dc46a808b6aa23bf50dd670f1f52ddc
git_describe: v5.19-rc7-13490-g9250d2f72dc4
git_ref: master
kernel_version: 5.19.0-rc8
kernel-config: https://builds.tuxbuild.com/2CWh3jswUGEkjvfXQPGXdOceMFH/config
artifact-location: https://builds.tuxbuild.com/2CWh3jswUGEkjvfXQPGXdOceMFH
toolchain: gcc-10
- Naresh
next prev parent reply other threads:[~2022-07-28 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 6:43 [next] arm: PM: domains: Delete usage of driver_deferred_probe_check_state() Naresh Kamboju
2022-07-27 18:49 ` Saravana Kannan
2022-07-28 5:34 ` Naresh Kamboju [this message]
2022-08-13 0:53 ` Saravana Kannan
2022-08-13 10:54 ` Naresh Kamboju
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=CA+G9fYv0DFZi2rMPQTHvK8yD7g0LZTxN76iKZxP4pi4+8Rstxg@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.