From owner-freebsd-arch Fri Dec 15 1:47:29 2000 From owner-freebsd-arch@FreeBSD.ORG Fri Dec 15 01:47:28 2000 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30]) by hub.freebsd.org (Postfix) with ESMTP id 4AC6437B402; Fri, 15 Dec 2000 01:47:26 -0800 (PST) Received: from dungeon.home (ppp168.dyn249.pacific.net.au [203.143.249.168]) by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id UAA03464; Fri, 15 Dec 2000 20:47:21 +1100 (EST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.11.1/8.9.3) with ESMTP id eBF89CC12453; Fri, 15 Dec 2000 18:09:13 +1000 (EST) (envelope-from mckay) Message-Id: <200012150809.eBF89CC12453@dungeon.home> To: John Baldwin Cc: arch@FreeBSD.ORG Subject: Re: kthread API References: In-Reply-To: from John Baldwin at "Thu, 14 Dec 2000 21:55:36 +0000" Date: Fri, 15 Dec 2000 18:09:12 +1000 From: Stephen McKay Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 14th December 2000, John Baldwin wrote: >I'd like to make some of the kernel API's a little more consistent as far as >in their naming. The first one I'd like to tackle is the kthread API. I support this, and have made similar suggestions in the past, where I was partially successful. After you've fixed the ones you want, consider changing vm_object_{set,clear}_flag to vm_object_flag_{set,clear} to match the (good) naming style used by similar routines from vm_page.h. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message