From owner-freebsd-current@FreeBSD.ORG Mon Feb 23 00:45:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42EA816A4CE for ; Mon, 23 Feb 2004 00:45:36 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94FF343D1D for ; Mon, 23 Feb 2004 00:45:35 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i1N8jRkn002772; Mon, 23 Feb 2004 09:45:32 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Tor Egge From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 23 Feb 2004 05:31:57 GMT." <20040223.053157.71126882.Tor.Egge@cvsup.no.freebsd.org> Date: Mon, 23 Feb 2004 09:45:27 +0100 Message-ID: <2771.1077525927@critter.freebsd.dk> cc: current@freebsd.org Subject: Re: CAUTION! device megapatch committed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 08:45:36 -0000 Thanks, I must have been pretty sleepy to overlook those. One note: >+ LIST_REMOVE(si, si_hash); /* XXX: Please add locking here */ kern_conf itself is far from Giant safe yet, but supposedly, the lifetimes of the data structures are now well-defined enough that we can go that step soon. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.