Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261255AbVAHSyp (ORCPT ); Sat, 8 Jan 2005 13:54:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261259AbVAHSyp (ORCPT ); Sat, 8 Jan 2005 13:54:45 -0500 Received: from darwin.snarc.org ([81.56.210.228]:34449 "EHLO darwin.snarc.org") by vger.kernel.org with ESMTP id S261255AbVAHSyo (ORCPT ); Sat, 8 Jan 2005 13:54:44 -0500 Date: Sat, 8 Jan 2005 19:54:40 +0100 To: Jon Smirl Cc: lkml Subject: Re: kernel versions on Linus bk tree Message-ID: <20050108185440.GA8915@snarc.org> References: <9e473391050108102355c9a714@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9e473391050108102355c9a714@mail.gmail.com> X-Warning: Email may contain unsmilyfied humor and/or satire. User-Agent: Mutt/1.5.6+20040907i From: Vincent Hanquez Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 964 Lines: 23 On Sat, Jan 08, 2005 at 01:23:20PM -0500, Jon Smirl wrote: > I just came across a problem with the way the kernel is being > versioned. The DRM driver needs an IFDEF for the four level page table > change depending on kernel version built against. I used this: > #if LINUX_VERSION_CODE < 0x02060a you might probably use KERNEL_VERSION here which is more convenient: #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,10) > The problem is that 2.6.10 was released on kernel.org without the four > level change. But Linus bk which also has version 2.6.10 has the > change. Is there some way around this problem? include/linux/version.h is generated by the Makefile. This file do not come with the source. -- Vincent Hanquez - 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/