From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
Christian Zigotzky <chzigotzky@xenosoft.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Olof Johansson <olof@lixom.net>, Rob Herring <robh@kernel.org>,
Darren Stevens <darren@stevens-zone.net>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [PASEMI NEMO] Boot issue with the PowerPC updates 6.4-1
Date: Mon, 8 May 2023 20:20:03 +0700 [thread overview]
Message-ID: <85ca82b1-8a53-c0d7-e1b6-93288a6e129c@gmail.com> (raw)
In-Reply-To: <fa6de026-1444-7beb-197c-d6a637eef86e@leemhuis.info>
On 5/8/23 20:17, Linux regression tracking (Thorsten Leemhuis) wrote:
>> Why and how can you conclude that the culprit is e4ab08be5b4902 ("powerpc/isa-bridge:
>> Remove open coded "ranges" parsing") rather than powerpc PR merge commit
>> 70cc1b5307e8ee ("Merge tag 'powerpc-6.4-1' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux")?
>
> I looked at the thread and noticed it was mentioned later (
> https://lore.kernel.org/all/3fa42c8c-09bd-d0f0-401b-315b484f4bb0@xenosoft.de/
> ).
>
Oops, I wasn't seeing the whole thread. Thanks anyway.
--
An old man doll... just what I always wanted! - Clara
WARNING: multiple messages have this Message-ID (diff)
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
Christian Zigotzky <chzigotzky@xenosoft.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Olof Johansson <olof@lixom.net>,
Darren Stevens <darren@stevens-zone.net>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Christian Zigotzky <info@xenosoft.de>,
Rob Herring <robh@kernel.org>
Subject: Re: [PASEMI NEMO] Boot issue with the PowerPC updates 6.4-1
Date: Mon, 8 May 2023 20:20:03 +0700 [thread overview]
Message-ID: <85ca82b1-8a53-c0d7-e1b6-93288a6e129c@gmail.com> (raw)
In-Reply-To: <fa6de026-1444-7beb-197c-d6a637eef86e@leemhuis.info>
On 5/8/23 20:17, Linux regression tracking (Thorsten Leemhuis) wrote:
>> Why and how can you conclude that the culprit is e4ab08be5b4902 ("powerpc/isa-bridge:
>> Remove open coded "ranges" parsing") rather than powerpc PR merge commit
>> 70cc1b5307e8ee ("Merge tag 'powerpc-6.4-1' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux")?
>
> I looked at the thread and noticed it was mentioned later (
> https://lore.kernel.org/all/3fa42c8c-09bd-d0f0-401b-315b484f4bb0@xenosoft.de/
> ).
>
Oops, I wasn't seeing the whole thread. Thanks anyway.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-05-08 13:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 2:22 [PASEMI NEMO] Boot issue with the PowerPC updates 6.4-1 Christian Zigotzky
2023-05-02 8:17 ` Christophe Leroy
2023-05-02 9:28 ` Michael Ellerman
2023-05-03 15:46 ` Christian Zigotzky
2023-05-03 16:27 ` Christophe Leroy
2023-05-03 16:51 ` Rob Herring
2023-05-03 17:28 ` Christian Zigotzky
2023-05-03 17:44 ` Christian Zigotzky
2023-05-03 18:15 ` Rob Herring
2023-05-04 4:51 ` Michael Ellerman
2023-05-05 4:48 ` Christian Zigotzky
2023-05-05 14:19 ` Rob Herring
2023-05-08 11:29 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-05-08 11:29 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-05-08 12:49 ` Michael Ellerman
2023-05-08 13:15 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-08 12:58 ` Bagas Sanjaya
2023-05-08 12:58 ` Bagas Sanjaya
2023-05-08 13:17 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-08 13:17 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-08 13:20 ` Bagas Sanjaya [this message]
2023-05-08 13:20 ` Bagas Sanjaya
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=85ca82b1-8a53-c0d7-e1b6-93288a6e129c@gmail.com \
--to=bagasdotme@gmail.com \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olof@lixom.net \
--cc=regressions@lists.linux.dev \
--cc=robh@kernel.org \
--cc=rtd2@xtra.co.nz \
/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.