From: Juergen Gross <jgross@suse.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH v2] s390/kvm: avoid hypfs error message
Date: Thu, 11 Aug 2022 10:14:55 +0200 [thread overview]
Message-ID: <040024a3-77dd-8869-1e64-0a67a438d1f6@suse.com> (raw)
In-Reply-To: <YrBarz+NVJmS+bBb@tuxmaker.boeblingen.de.ibm.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 641 bytes --]
On 20.06.22 13:31, Alexander Gordeev wrote:
> On Mon, Jun 20, 2022 at 11:45:34AM +0200, Juergen Gross wrote:
>> When booting under KVM the following error messages are issued:
>>
>> hypfs.7f5705: The hardware system does not support hypfs
>> hypfs.7a79f0: Initialization of hypfs failed with rc=-61
>>
>> Demote the severity of first message from "error" to "info" and issue
>> the second message only in other error cases.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>
> Applied, thanks!
Hmm, applied to which tree and branch?
I would have thought this patch should have reached upstream by now...
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2022-08-11 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 9:45 [PATCH v2] s390/kvm: avoid hypfs error message Juergen Gross
2022-06-20 9:47 ` Heiko Carstens
2022-06-20 9:48 ` Christian Borntraeger
2022-06-20 11:31 ` Alexander Gordeev
2022-08-11 8:14 ` Juergen Gross [this message]
2022-08-11 14:49 ` Alexander Gordeev
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=040024a3-77dd-8869-1e64-0a67a438d1f6@suse.com \
--to=jgross@suse.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
/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