From: Christoph Hellwig <hch@infradead.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: akpm@osdl.org, wein@de.ibm.com, Horst.Hummel@de.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch 3/3] s390: dasd extended error reporting module.
Date: Fri, 16 Dec 2005 13:47:54 +0000 [thread overview]
Message-ID: <20051216134754.GA23964@infradead.org> (raw)
In-Reply-To: <20051216132953.GD8877@skybase.boeblingen.de.ibm.com>
On Fri, Dec 16, 2005 at 02:29:53PM +0100, Martin Schwidefsky wrote:
> From: Stefan Weinhuber <wein@de.ibm.com>
>
> [patch 3/3] s390: dasd extended error reporting module.
>
> The DASD extended error reporting is a facility that allows to
> get detailed information about certain problems in the DASD I/O.
> This information can be used to implement fail-over applications
> that can recover these problems.
>
> Signed-off-by: Stefan Weinhuber <wein@de.ibm.com>
> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
>
> ---
>
> arch/s390/kernel/compat_ioctl.c | 2
> drivers/s390/block/Kconfig | 14
> drivers/s390/block/Makefile | 2
> drivers/s390/block/dasd.c | 76 ++
> drivers/s390/block/dasd_3990_erp.c | 5
> drivers/s390/block/dasd_eckd.h | 3
> drivers/s390/block/dasd_eer.c | 1091 +++++++++++++++++++++++++++++++++++++
> drivers/s390/block/dasd_int.h | 37 +
> include/asm-s390/dasd.h | 15
> 9 files changed, 1237 insertions(+), 8 deletions(-)
>
> diff -urpN linux-2.6/arch/s390/kernel/compat_ioctl.c linux-2.6-patched/arch/s390/kernel/compat_ioctl.c
> --- linux-2.6/arch/s390/kernel/compat_ioctl.c 2005-12-16 10:56:42.000000000 +0100
> +++ linux-2.6-patched/arch/s390/kernel/compat_ioctl.c 2005-12-16 10:57:24.000000000 +0100
> @@ -63,6 +63,8 @@ COMPATIBLE_IOCTL(BIODASDSATTR)
> COMPATIBLE_IOCTL(BIODASDCMFENABLE)
> COMPATIBLE_IOCTL(BIODASDCMFDISABLE)
> COMPATIBLE_IOCTL(BIODASDREADALLCMB)
> +COMPATIBLE_IOCTL(BIODASDEERSET)
> +COMPATIBLE_IOCTL(BIODASDEERGET)
Nack, now new ioctls in compat_ioctl.c, please. In fact that file is
gone in -mm, so please submit this patch ontop of the -mm tree.
And is there a chance for a better interface than the notifier lists?
The code looks rather awkward because of it.
next prev parent reply other threads:[~2005-12-16 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 13:29 [patch 3/3] s390: dasd extended error reporting module Martin Schwidefsky
2005-12-16 13:47 ` Christoph Hellwig [this message]
2005-12-16 14:33 ` Martin Schwidefsky
2005-12-16 14:35 ` Christoph Hellwig
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=20051216134754.GA23964@infradead.org \
--to=hch@infradead.org \
--cc=Horst.Hummel@de.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=wein@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