From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 18 Mar 2003 17:18:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 18 Mar 2003 17:18:27 -0500 Received: from havoc.daloft.com ([64.213.145.173]:10930 "EHLO havoc.gtf.org") by vger.kernel.org with ESMTP id ; Tue, 18 Mar 2003 17:18:26 -0500 Date: Tue, 18 Mar 2003 17:29:18 -0500 From: Jeff Garzik To: Andries.Brouwer@cwi.nl Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] dev_t [1/3] Message-ID: <20030318222918.GD23134@gtf.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 18, 2003 at 10:45:14PM +0100, Andries.Brouwer@cwi.nl wrote: > The first patch is the cdev-kill patch that I sent out > earlier. It is no use having two forms of chardev registration > in the source, and my version of the path of small modifications > does not pass through this version, although the final result > will not be that different. So, kill cdev_cachep, cdev_cache_init, > cdfind, cdget, cdput, inode->i_cdev, struct char_device. > All of this is dead code today. You're also removing refcount code... why not fix it up instead? I agree your patch is mostly correct from a "today" standpoint, but from a long term standpoint I think fixing up the code as intended would be the best path. It would be silly to remove this code only to add it again. Jeff