linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 206123] aacraid ( PM8068) and iommu=nobypass Frozen PHB error  on ppc64
Date: Fri, 11 Sep 2020 06:22:50 +0000	[thread overview]
Message-ID: <bug-206123-11613-tDXvVzokPc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206123-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=206123

--- Comment #14 from gyakovlev@gentoo.org ---
Hi Sagar,

testing on 5.8 is a bit problematic for me, because some things on that system
require 5.4 kernel.

Patch applies to 5.8, I assume it'll work just fine. No plans testing it.
I meant I'll be patching my kernels till the fix will be backported to release
versions of linux.

Thanks all for you help and attention, bug definitely can be closed from my
point of view.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-09-11  6:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08  5:59 [Bug 206123] New: aacraid ( PM8068) and iommu=nobypass Frozen PHB error on ppc64 bugzilla-daemon
2020-01-08  6:00 ` [Bug 206123] " bugzilla-daemon
2020-01-08  6:05 ` bugzilla-daemon
2020-01-08  6:25 ` bugzilla-daemon
2020-04-20  3:18 ` bugzilla-daemon
2020-04-20 18:41 ` bugzilla-daemon
2020-05-06  8:21 ` bugzilla-daemon
2020-09-09 19:07 ` bugzilla-daemon
2020-09-09 23:07 ` bugzilla-daemon
2020-09-09 23:14 ` bugzilla-daemon
2020-09-10  1:32 ` bugzilla-daemon
2020-09-10  1:46 ` bugzilla-daemon
2020-09-11  3:38 ` bugzilla-daemon
2020-09-11  6:16 ` bugzilla-daemon
2020-09-11  6:22 ` bugzilla-daemon [this message]
2020-09-11 18:30 ` bugzilla-daemon
2020-09-11 18:39 ` bugzilla-daemon
2020-09-11 18:48 ` bugzilla-daemon

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=bug-206123-11613-tDXvVzokPc@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.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;
as well as URLs for NNTP newsgroup(s).