All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
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 15:33:09 +0100	[thread overview]
Message-ID: <1134743589.5495.16.camel@localhost.localdomain> (raw)
In-Reply-To: <20051216134754.GA23964@infradead.org>

On Fri, 2005-12-16 at 13:47 +0000, Christoph Hellwig wrote:
> 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.
> > 
> 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.

Hmm, that's true. In that case it's probably best to wait until the
first wave of patches out of -mm have hit the git tree and then I
recreate the patch from our internal tree. The current patch dependecies
are starting to make my head ache.

> And is there a chance for a better interface than the notifier lists?
> The code looks rather awkward because of it.

Older versions of the code had an own registration function for a
callback pointer for the events. It only accepted one user and sort of
reinvented the notify functionality. I'd prefer notifiers compare to the
old solution. If you have a clever idea, we are listening.

On a side not, Arnd just told my about the bug in the dasd_eckd
discipline. We need to check the discipline in the eckd specific ioctls.
I'll tell the appropriate people (well in fact I already did because
they are on CC:). As for adding a per discipline .ioctl function, that
won't work because of cmb and eer. These modules do not implement a
discipline but still have to add ioctls.

-- 
blue skies,
   Martin

Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH



  reply	other threads:[~2005-12-16 14:33 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
2005-12-16 14:33   ` Martin Schwidefsky [this message]
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=1134743589.5495.16.camel@localhost.localdomain \
    --to=schwidefsky@de.ibm.com \
    --cc=Horst.Hummel@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.