Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755956AbXIUINg (ORCPT ); Fri, 21 Sep 2007 04:13:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752712AbXIUINU (ORCPT ); Fri, 21 Sep 2007 04:13:20 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:45949 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750718AbXIUINT (ORCPT ); Fri, 21 Sep 2007 04:13:19 -0400 Date: Fri, 21 Sep 2007 09:08:08 +0100 From: Christoph Hellwig To: Randy Dunlap Cc: Sam Ravnborg , Christoph Hellwig , David Wilder , Andi Kleen , linux-kernel@vger.kernel.org, akpm@linux-foundation.org, Linus Torvalds Subject: Re: Test harness in the kernel for new syscalls? [Was: Trace code and documentation (updated)] Message-ID: <20070921080808.GB29050@infradead.org> Mail-Followup-To: Christoph Hellwig , Randy Dunlap , Sam Ravnborg , David Wilder , Andi Kleen , linux-kernel@vger.kernel.org, akpm@linux-foundation.org, Linus Torvalds References: <1190177218.3190.18.camel@lc4eb748232119.ibm.com> <46F12ED7.3060605@us.ibm.com> <20070919162018.GA16237@infradead.org> <20070919095223.83bd8226.randy.dunlap@oracle.com> <20070919165507.GA18973@infradead.org> <20070919174845.GD3115@uranus.ravnborg.org> <20070919175109.GA23889@infradead.org> <20070919180115.GE3115@uranus.ravnborg.org> <20070920215042.38fd3546.randy.dunlap@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070920215042.38fd3546.randy.dunlap@oracle.com> User-Agent: Mutt/1.4.2.3i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1171 Lines: 20 On Thu, Sep 20, 2007 at 09:50:42PM -0700, Randy Dunlap wrote: > so kernel sample code goes in the new samples/ directory, > and userspace sample code gets pushed to util-linux ? I'm not sure we want to have purely sample code in util-linux, but rather extended sample code that makes some use. So if you're writing user space sample code for your new feature make sure it's somewhat production quality, has a useful interface and write a little manpage for it. That'll also help us to win sysdamins hearts back because BSD and solaris already have all these neat little tools that need to be hacked from scratch in perl on Linux. For kernel code a samples dir might make sense because say a demo of the firmware loader (one of those things in Documentation/ right now) of course never can be "real" code. OTOH a fork probe as provided with the tracing code sounds more like a real thing that should go into drivers/misc/. - 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/