mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Lorenzo Stoakes <lstoakes@gmail.com>, Will Deacon <will@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	wangkefeng.wang@huawei.com, catalin.marinas@arm.com,
	ardb@kernel.org
Subject: Re: arm64: perf test 26 rpi4 oops
Date: Tue, 01 Aug 2023 01:27:34 +0200	[thread overview]
Message-ID: <42ad26cb6c98e028a331f5d73abf85bd965ff89d.camel@gmx.de> (raw)
In-Reply-To: <CAA5enKYaZ-daLeL3amr2QrQjtUdK=P8B+VbJdea7cB77QWY-eQ@mail.gmail.com>

On Mon, 2023-07-31 at 22:54 +0100, Lorenzo Stoakes wrote:
>
> Posted a fix at:-
>
> https://lore.kernel.org/all/20230731215021.70911-1-lstoakes@gmail.com/
>
> Please give that a go and indicate whether that resolves the issue.

Yup, that fixed the oops issue.

	-Mike

  reply	other threads:[~2023-07-31 23:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  4:06 Mike Galbraith
2023-07-28 14:18 ` Will Deacon
2023-07-28 15:12   ` Mike Galbraith
2023-07-28 15:23     ` Will Deacon
2023-07-28 16:35       ` Mike Galbraith
2023-07-29 16:30     ` Mike Galbraith
2023-07-30  5:54   ` Mike Galbraith
2023-07-30 11:01     ` Mike Galbraith
2023-07-30 16:09   ` Mike Galbraith
2023-07-31 10:43     ` Will Deacon
2023-07-31 11:37       ` Mike Galbraith
2023-07-31 11:52       ` Will Deacon
2023-07-31 16:07         ` Mike Galbraith
2023-07-31 21:08         ` Lorenzo Stoakes
2023-07-31 21:54           ` Lorenzo Stoakes
2023-07-31 23:27             ` Mike Galbraith [this message]
2023-07-31 23:48               ` Mike Galbraith
2023-08-01  0:33                 ` Mike Galbraith
2023-08-01  4:34                 ` Mike Galbraith
2023-08-01  7:27                   ` Will Deacon
2023-08-01  8:39                     ` Mike Galbraith

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=42ad26cb6c98e028a331f5d73abf85bd965ff89d.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lstoakes@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®