public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC/git patch] move samples/ to Documentation/markers/
Date: Wed, 24 Oct 2007 09:19:05 -0400	[thread overview]
Message-ID: <471F4649.3000000@garzik.org> (raw)
In-Reply-To: <20071024130557.GA18610@Krystal>

Honestly, I don't care at all about building the code.  If that's what 
you want, great.

My objection is more to adding a samples/ directory, which is contra to 
past experience:

A new net driver sample should go in drivers/net/ like the existing 
skeleton files I already listed, not samples/net/.  A top-level 
"samples/" seems like it exists only duplicate the rest of the tree 
hierarchy.

	Jeff




  reply	other threads:[~2007-10-24 13:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24  9:52 [RFC/git patch] move samples/ to Documentation/markers/ Jeff Garzik
2007-10-24 10:10 ` Sam Ravnborg
2007-10-24 13:05 ` Mathieu Desnoyers
2007-10-24 13:19   ` Jeff Garzik [this message]
2007-10-24 16:12     ` Randy Dunlap
2007-10-24 16:17       ` Sam Ravnborg
2007-10-24 17:31       ` [RFC] create instrumentation/ directory Mathieu Desnoyers
2007-10-24 17:48         ` Randy Dunlap
2007-10-25 20:08         ` Valdis.Kletnieks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=471F4649.3000000@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=fche@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=randy.dunlap@oracle.com \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox