public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Horst Hummel <horst.hummel@de.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kernel <linux-kernel@vger.kernel.org>,
	heiko <heicars2@de.ibm.com>, Stefan Weinhuber <wein@de.ibm.com>,
	Martin <mschwid2@de.ibm.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 0/5] new dasd ioctl patchkit
Date: Tue, 14 Feb 2006 17:53:08 +0100	[thread overview]
Message-ID: <1139935988.6183.5.camel@localhost.localdomain> (raw)


> Here's a new patchkit to fix the dasd ioctl mess, against
> 2.6.16-rc2-mm1. I've built an s390 crosscompiler to compile-test them
and
> I've booted the resulting kernel with a debian image in hercules (not
that
> this excercises the ioctl path a whole lot, but I didn't find tools
that
> actually used any of these ioctls).
>
Thanks for doing some test this time. 
If I got that right, there is no big difference related to your last
proposal.

Unfortunately neither me nor Stefan W. got an answer on the question
about being more precise on 'ioctl mess' or any other statements
like 'adds more junk to already crappy code'.

We can't see - and you did not specify - reasons why the current
approach does not work. Therefore I don't see any urgency to change
that NOW instead of discuss the design change (consulting Martin - 
he will be back next week) and do the ioctl change when we have an 
agreed solution including ALL components. 

I agree that you proposal is straight forward and looks more pretty,
but I don't like the approach to just delete code that doesn't fit
your ideas.

As already mentioned we are currently working on a solution to move
the whole cmb-code out of the DASD device driver. 
In addintion I talked to Stefan W. and he is doing some evalutation
about possible solution for the eer_module on how adapt that module
to your proposal while keeping the functionality. 

As I already said, I would like to wait for final solution and 
don't apply the patches NOW.

regards
Horst Hummel


             reply	other threads:[~2006-02-14 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14 16:53 Horst Hummel [this message]
2006-02-14 19:09 ` [PATCH 0/5] new dasd ioctl patchkit Christoph Hellwig
2006-02-15 14:23   ` Carsten Otte
2006-02-15 20:03     ` Andrew Morton
2006-02-16  5:46       ` Heiko Carstens
2006-02-15 21:14   ` Stefan Weinhuber
  -- strict thread matches above, loose matches on Subject: below --
2006-02-12 17:38 Christoph Hellwig
2006-02-13  7:04 ` Heiko Carstens

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=1139935988.6183.5.camel@localhost.localdomain \
    --to=horst.hummel@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --cc=heicars2@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mschwid2@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