Date: Tue, 20 Jul 1999 14:34:24 -0400 (EDT) From: Alfred Perlstein <bright@rush.net> To: Poul-Henning Kamp <phk@FreeBSD.ORG> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/dev/vn vn.c src/sys/kern kern_conf.c vfs_subr.c src/sys/miscfs/specfs spec_vnops.c specdev.h src/sys/sys conf.h param.h types.h vnode.h src/sys/ufs/mfs mfs_vfsops.c Message-ID: <Pine.BSF.3.96.990720142949.27774F-100000@cygnus.rush.net> In-Reply-To: <199907200947.CAA01573@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20 Jul 1999, Poul-Henning Kamp wrote: > phk 1999/07/20 02:47:56 PDT > > Modified files: > sys/dev/vn vn.c > sys/kern kern_conf.c vfs_subr.c > sys/miscfs/specfs spec_vnops.c specdev.h > sys/sys conf.h param.h types.h vnode.h > sys/ufs/mfs mfs_vfsops.c > Log: > Now a dev_t is a pointer to struct specinfo which is shared by all specdev > vnodes referencing this device. ... Poul-Henning, I've been watching your dev_t changes in CVS, am I correct to assume that they are for the purpose of providing an API for manipulating device status/info without having to hack into more private data, also to insure that device drivers don't get too entrenched into subsystems that may change at a later date? And also to provide a more meaningful looking api instead of cdevsw[blah[blah2]+x] that seemed to be prevelant throughout the source last I checked? Any other reasons? Just interested. thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990720142949.27774F-100000>