From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
KVM <kvm@vger.kernel.org>, Cornelia Huck <cohuck@redhat.com>,
David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Julian Wiedmann <jwi@linux.ibm.com>,
Stefan Haberland <sth@linux.ibm.com>,
Jan Hoeppner <hoeppner@linux.ibm.com>
Subject: Re: [PATCH] KVM: s390: ENOTSUPP -> EOPNOTSUPP fixups
Date: Thu, 5 Dec 2019 17:09:30 +0100 [thread overview]
Message-ID: <20191205160930.GA13800@osiris> (raw)
In-Reply-To: <26f905be-3f09-3b3b-3008-ef64fc93e36c@de.ibm.com>
On Thu, Dec 05, 2019 at 02:16:02PM +0100, Christian Borntraeger wrote:
> On 05.12.19 14:09, Thomas Huth wrote:
> > On 05/12/2019 13.51, Christian Borntraeger wrote:
> >> There is no ENOTSUPP for userspace
> >>
> >> Reported-by: Julian Wiedmann <jwi@linux.ibm.com>
> >> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> >> ---
> >> - return -ENOTSUPP;
> >> + return -EOPNOTSUPP;
> > There seems to be another one in arch/s390/include/asm/uv.h, are you
> > going to fix that, too?
> I looked into that but it seemed that this is not exposed to
> userspace and just kept internal.
Could you remove that one as well, please? Otherwise people start
copy-pasting this (again). I thought we got rid of them all, and now
they crept in again.
Same for dasd ioctl code...
next prev parent reply other threads:[~2019-12-05 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 12:51 [PATCH] KVM: s390: ENOTSUPP -> EOPNOTSUPP fixups Christian Borntraeger
2019-12-05 13:05 ` Cornelia Huck
2019-12-05 13:09 ` Thomas Huth
2019-12-05 13:16 ` Christian Borntraeger
2019-12-05 16:09 ` Heiko Carstens [this message]
2019-12-05 17:07 ` Christian Borntraeger
2019-12-05 14:50 ` Christian Borntraeger
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=20191205160930.GA13800@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=hoeppner@linux.ibm.com \
--cc=jwi@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sth@linux.ibm.com \
--cc=thuth@redhat.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