Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265544AbUFXUiK (ORCPT ); Thu, 24 Jun 2004 16:38:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265537AbUFXUiE (ORCPT ); Thu, 24 Jun 2004 16:38:04 -0400 Received: from pfepa.post.tele.dk ([195.41.46.235]:38927 "EHLO pfepa.post.tele.dk") by vger.kernel.org with ESMTP id S265544AbUFXUgx (ORCPT ); Thu, 24 Jun 2004 16:36:53 -0400 Date: Thu, 24 Jun 2004 22:49:52 +0200 From: Sam Ravnborg To: Patrick McFarland Cc: Sam Ravnborg , linux-kernel@vger.kernel.org Subject: Re: RFC: Testing for kernel features in external modules Message-ID: <20040624204952.GA4700@mars.ravnborg.org> Mail-Followup-To: Patrick McFarland , Sam Ravnborg , linux-kernel@vger.kernel.org References: <20040624203043.GA4557@mars.ravnborg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 992 Lines: 24 On Thu, Jun 24, 2004 at 04:24:01PM -0400, Patrick McFarland wrote: > On Thu, 24 Jun 2004 22:30:43 +0200, Sam Ravnborg wrote: > > > > The last couple of kbuild patches has put attention to testing for > > features in the kernel so an external modules can stay compatible > > with a broad range of kernels. > > Since vendors backport patches then testing for the kernel version is not > > an option, so other means are reqired. > > > > Two approaches are in widespread use: > > a) grep kernel headers > > b) Try to compile a small .c file (nvidia is a good example) > > Why can't you check the .config file to see if features are enabled? Features in a broad sense so API changes with respect to types and function calls Sam - 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/