Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 15 Nov 2002 13:03:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 15 Nov 2002 13:03:19 -0500 Received: from leibniz.math.psu.edu ([146.186.130.2]:38628 "EHLO math.psu.edu") by vger.kernel.org with ESMTP id ; Fri, 15 Nov 2002 13:03:18 -0500 Date: Fri, 15 Nov 2002 13:10:12 -0500 (EST) From: Alexander Viro To: Joe Thornber cc: "chandrasekhar.nagaraj" , linux-kernel@vger.kernel.org Subject: Re: Path Name to kdev_t In-Reply-To: <20021115161536.GA6654@reti> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 831 Lines: 23 On Fri, 15 Nov 2002, Joe Thornber wrote: > On Thu, Nov 14, 2002 at 07:19:16PM +0530, chandrasekhar.nagaraj wrote: > > Hi, > > > > In one of the part of my driver module , I have a path name to a device file > > (for eg:- /dev/hda1) .Now if I want to obtain the associated major number > > and minor number i.e. device ID(kdev_t) of this file what would be the > > procedure? > > I think this should be standard function, I'm sure lots of people are > duplicating this code. For 2.4 kernels: No, it really shouldn't. You should _NOT_ mess with kdev_t - use real objects instead. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/