From owner-freebsd-current Sun Oct 22 14:47:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 2C92537B4FE for ; Sun, 22 Oct 2000 14:47:32 -0700 (PDT) Date: Sun, 22 Oct 2000 22:47:30 +0100 From: David Malone To: Jesper Skriver Cc: Poul-Henning Kamp , Garrett Rooney , Andrea Campi , current@FreeBSD.ORG, josh@zipperup.org, robd@gmx.net Subject: Re: Junior Kernel Hacker Task: M_ZERO Message-ID: <20001022224730.A96694@salmon.maths.tcd.ie> References: <7263.972191191@critter> <200010221854.aa75575@salmon.maths.tcd.ie> <20001022210747.A4324@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001022210747.A4324@skriver.dk>; from jesper@skriver.dk on Sun, Oct 22, 2000 at 09:07:48PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 22, 2000 at 09:07:48PM +0200, Jesper Skriver wrote: > What about using something like > > #if defined(__FreeBSD__) && __FreeBSD_version >= 5xxxxx > > This would probably make it easier for multi OS code, and also make > it easier to MFC some of the affected code into -stable ?? I think it's probably better to allow people to choose how to do it in their own code. Justin has already asked that we hang off on making any changes to the cam code until the M_ZERO flag is also available in -stable. Given that it is a relatively trivial change to add the M_ZERO flag I presume it can be MFCed quite quickly. We don't need to merge back the patch enabling it's use though. It's probably best kept as a "forward compatablilty" thing. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message