All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	jroedel@suse.de
Cc: Darren Stevens <darren@stevens-zone.net>,
	Christoph Hellwig <hch@lst.de>, "R.T.Dickinson" <rtd2@xtra.co.nz>,
	Christian Zigotzky <info@xenosoft.de>
Subject: Re: Boot issue with the latest Git kernel
Date: Sun, 7 Jun 2020 15:27:16 +0200	[thread overview]
Message-ID: <4dcedace-f3e6-1258-86fc-665666955946@xenosoft.de> (raw)
In-Reply-To: <7bf97562-3c6d-de73-6dbd-ccca275edc7b@xenosoft.de>

Hi All,

It seems, someone has fixed the boot issue. The latest Git kernel boots 
on my PowerPC machines.

Thanks,
Christian


On 05 June 2020 at 6:23 pm, Christian Zigotzky wrote:
> On 04 June 2020 at 7:15 pm, Christophe Leroy wrote:
>> Yes today's linux-next boots on my powerpc 8xx board.
>>
>> Christophe
> Hello Christophe,
>
> Thanks for testing.
>
> I was able to perform a 'git bisect' [1] and identified the bad 
> commit. [2] I reverted this commit and after that the kernel boots and 
> works without any problems.
>
> Could you please check this commit?
>
> Thanks,
> Christian
>
>
> [1] https://forum.hyperion-entertainment.com/viewtopic.php?p=50772#p50772
> [2] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2ba3e6947aed9bb9575eb1603c0ac6e39185d32a


  reply	other threads:[~2020-06-07 13:35 UTC|newest]

Thread overview: 29+ 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
2020-06-05 16:23         ` Christian Zigotzky
2020-06-07 13:27           ` Christian Zigotzky [this message]
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-10 11:23                   ` Christian Zigotzky
2020-06-11 14:47                   ` Christian Zigotzky
2020-06-11 14:47                     ` Christian Zigotzky
2020-06-12 13:01                     ` Christian Zigotzky
2020-06-12 13:01                       ` Christian Zigotzky
2020-06-14  8:50                       ` Nicholas Piggin
2020-06-14  8:50                         ` Nicholas Piggin
2020-06-14 12:53                       ` Nicholas Piggin
2020-06-14 12:53                         ` Nicholas Piggin
2020-06-14 14:52                         ` Christian Zigotzky
2020-06-14 14:52                           ` Christian Zigotzky
2020-06-14 23:39                           ` Christian Zigotzky
2020-06-14 23:39                             ` Christian Zigotzky
2020-06-15  7:34                             ` Christian Zigotzky
2020-06-15  7:34                               ` Christian Zigotzky
2020-06-25  9:38                             ` 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=4dcedace-f3e6-1258-86fc-665666955946@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=christophe.leroy@csgroup.eu \
    --cc=darren@stevens-zone.net \
    --cc=hch@lst.de \
    --cc=info@xenosoft.de \
    --cc=jroedel@suse.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 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.