public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Ric Wheeler <ric@emc.com>
Cc: Christoph Hellwig <hch@lst.de>,
	akpm@osdl.org, arnd@arndb.de, linux-kernel@vger.kernel.org,
	"saparnis, carol" <saparnis_carol@emc.com>
Subject: Re: [PATCH 2/2] dasd: remove dynamic ioctl registration
Date: Wed, 11 Jan 2006 10:16:27 +0100	[thread overview]
Message-ID: <1136970987.6147.14.camel@localhost.localdomain> (raw)
In-Reply-To: <43BE7EE4.3010203@emc.com>

On Fri, 2006-01-06 at 09:29 -0500, Ric Wheeler wrote:
> 
> Christoph Hellwig wrote:
> 
> >>If you could hold off just a couple of weeks, I hope that we can get 
> >>through our EMC process junk and get the GPL'ed patch out to fix the 
> >>symmetrix support part of this rolled in as well,
> >>    
> >>
> >
> >Why?  We never do things to support legally questionable binary modules.
> >And on the practical side, does emc even ship modules for -mm release?
> >What's the point of not putting it into -mm?
> >  
> >
> No need for an EMC module, I think that we can issue a simple  patch to 
> dasd.c that removes the (silly) binary module that was there.
> 
> I would prefer that the clean up not break one of the few (and 
> relatively common) devices supported by the dasd.c driver. If for no 
> other reason, it would seem to make it more likely to be able test the 
> existing patch properly.

The patch we got from EMC is for 2.4 and in its current form would never
have worked for 2.6 anyway. So 2.6 is already broken, no reason to hold
off the ioctl removal patch. We'll come up with a cleaned up solution.

Christoph, please go ahead and push the patch to Andrew. 

-- 
blue skies,
   Martin

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



  reply	other threads:[~2006-01-11  9:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16 14:33 [PATCH 2/2] dasd: remove dynamic ioctl registration Christoph Hellwig
2005-12-16 14:58 ` Martin Schwidefsky
2005-12-16 15:00   ` Christoph Hellwig
2005-12-16 16:32     ` Martin Schwidefsky
2005-12-16 16:38       ` Christoph Hellwig
2005-12-16 16:13         ` Ric Wheeler
2005-12-16 19:30           ` Martin Schwidefsky
2006-01-06 11:01 ` Christoph Hellwig
2006-01-06 14:18   ` Ric Wheeler
2006-01-06 14:21     ` Christoph Hellwig
2006-01-06 14:29       ` Ric Wheeler
2006-01-11  9:16         ` Martin Schwidefsky [this message]
2006-01-17 13:35           ` Christoph Hellwig
2006-01-17 20:50             ` Andrew Morton

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=1136970987.6147.14.camel@localhost.localdomain \
    --to=schwidefsky@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=arnd@arndb.de \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ric@emc.com \
    --cc=saparnis_carol@emc.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