From: Nick Andrew <nick@nick-andrew.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org, samr <sam@ravnborg.org>
Subject: Re: [PATCH v2] documentation: build source files in Documentation sub-dir
Date: Thu, 10 Apr 2008 08:52:30 +1000 [thread overview]
Message-ID: <20080409225229.GC18242@tull.net> (raw)
In-Reply-To: <20080409123551.42c5da0d.randy.dunlap@oracle.com>
On Wed, Apr 09, 2008 at 12:35:51PM -0700, Randy Dunlap wrote:
> +##oops, this is a kernel module::hostprogs-y := procfs_example
Is this intentional? It looks like you commented-out a mistake.
Nick.
next prev parent reply other threads:[~2008-04-09 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 19:45 [PATCH] documentation: build source files in Documentation sub-dir Randy Dunlap
2008-04-08 20:46 ` Andrew Morton
2008-04-09 19:35 ` [PATCH v2] " Randy Dunlap
2008-04-09 21:54 ` Andrew Morton
2008-04-11 0:56 ` Randy Dunlap
2008-04-11 1:11 ` Andrew Morton
2008-04-13 14:05 ` Thomas Gleixner
2008-04-09 22:52 ` Nick Andrew [this message]
2008-04-09 23:53 ` Randy Dunlap
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=20080409225229.GC18242@tull.net \
--to=nick@nick-andrew.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sam@ravnborg.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