From: Greg Smith <gsmith@nc.rr.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com
Subject: Re: [patch 16/17] s390: multiple subchannel sets support.
Date: Mon, 27 Feb 2006 17:02:15 -0500 [thread overview]
Message-ID: <1141077735.3509.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20060227091546.2d63209b@gondolin.boeblingen.de.ibm.com>
On Mon, 2006-02-27 at 09:15 +0100, Cornelia Huck wrote:
> The architecture seems to disagree somewhat :)
You mean you all got doc?? What kind of hackers R u guys ;-)
> anyway... I'd prefer the following patch:
Works for me (tm)
> s390: Improve response code handling in chsc_enable_facility().
>
> Rather than checking for some known failures, check positively for the
> success response code 0x0001 and return -EIO for unrecognized failure
> response codes.
>
> Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
>
> chsc.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/s390/cio/chsc.c b/drivers/s390/cio/chsc.c
> index 8cf9905..f4183d6 100644
> --- a/drivers/s390/cio/chsc.c
> +++ b/drivers/s390/cio/chsc.c
> @@ -1115,6 +1115,9 @@ chsc_enable_facility(int operation_code)
> goto out;
> }
> switch (sda_area->response.code) {
> + case 0x0001: /* everything ok */
> + ret = 0;
> + break;
> case 0x0003: /* invalid request block */
> case 0x0007:
> ret = -EINVAL;
> @@ -1123,6 +1126,8 @@ chsc_enable_facility(int operation_code)
> case 0x0101: /* facility not provided */
> ret = -EOPNOTSUPP;
> break;
> + default: /* something went wrong */
> + ret = -EIO;
> }
> out:
> free_page((unsigned long)sda_area);
Many thanks,
Greg Smith
next prev parent reply other threads:[~2006-02-27 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 11:12 Greg Smith
2006-02-27 8:15 ` Cornelia Huck
2006-02-27 22:02 ` Greg Smith [this message]
2006-03-13 22:18 ` Greg Smith
2006-03-14 8:29 ` Cornelia Huck
-- strict thread matches above, loose matches on Subject: below --
2005-12-09 15:29 Martin Schwidefsky
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=1141077735.3509.2.camel@localhost.localdomain \
--to=gsmith@nc.rr.com \
--cc=cornelia.huck@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.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
Powered by JetHome