From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: Darren Stevens <darren@stevens-zone.net>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Christoph Hellwig <hch@lst.de>, "R.T.Dickinson" <rtd2@xtra.co.nz>
Subject: Re: Boot issue with the latest Git kernel
Date: Thu, 4 Jun 2020 19:15:01 +0200 [thread overview]
Message-ID: <014e1268-dcce-61a3-8bcd-a06c43e0dfaf@csgroup.eu> (raw)
In-Reply-To: <067BBAB3-19B6-42C6-AA9F-B9F14314255C@xenosoft.de>
Le 04/06/2020 à 17:53, Christian Zigotzky a écrit :
>
>
>> On 4. Jun 2020, at 16:29, Christophe Leroy <christophe.leroy@csgroup.eu> wrote:
>>
>> And are you able to perform a 'git bisect' to identify the guilty commit ?
>>
>> Thanks
>> Christophe
>
> Hello Christophe,
>
> Unfortunately I haven’t had time to bisect the latest Git kernel. Does it boot on your PowerPC machine?
>
Yes today's linux-next boots on my powerpc 8xx board.
Christophe
next prev parent reply other threads:[~2020-06-04 17:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 14:16 Boot issue with the latest Git kernel Christian Zigotzky
2020-06-04 14:26 ` Christophe Leroy
2020-06-04 14:29 ` Christophe Leroy
2020-06-04 15:46 ` Christian Zigotzky
2020-06-04 15:53 ` Christian Zigotzky
2020-06-04 17:15 ` Christophe Leroy [this message]
2020-06-05 16:23 ` Christian Zigotzky
2020-06-07 13:27 ` Christian Zigotzky
2020-06-07 14:07 ` Aneesh Kumar K.V
2020-06-09 22:18 ` PowerPC KVM-PR issue Christian Zigotzky
2020-06-10 9:06 ` Christian Zigotzky
2020-06-10 11:23 ` Christian Zigotzky
2020-06-11 14:47 ` Christian Zigotzky
2020-06-12 13:01 ` Christian Zigotzky
2020-06-14 8:50 ` Nicholas Piggin
2020-06-14 12:53 ` Nicholas Piggin
2020-06-14 14:52 ` Christian Zigotzky
2020-06-14 23:39 ` Christian Zigotzky
2020-06-15 7:34 ` Christian Zigotzky
2020-06-25 9:38 ` Christian Zigotzky
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=014e1268-dcce-61a3-8bcd-a06c43e0dfaf@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=hch@lst.de \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).