From: Joe Perches <joe@perches.com>
To: Rob Landley <rob@landley.net>, Johannes Berg <johannes@sipsolutions.net>
Cc: mm-commits@vger.kernel.org, fengguang.wu@intel.com,
linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: docproc.c:
Date: Thu, 18 Jul 2013 19:07:29 -0700 [thread overview]
Message-ID: <1374199649.1949.143.camel@joe-AO722> (raw)
In-Reply-To: <51e89d4a.EzMm4kY3e/JyyINM%akpm@linux-foundation.org>
On Thu, 2013-07-18 at 18:58 -0700, akpm@linux-foundation.org wrote:
> > docproc: kernel/printk.c: No such file or directory
> So rename the file.
[]
> Documentation/DocBook/device-drivers.tmpl | 2 +-
[]
> @@ -84,7 +84,7 @@ X!Iinclude/linux/kobject.h
[]
> -!Ekernel/printk.c
> +!Ekernel/printk/printk.c
Hey Rob/Johannes.
I renamed kernel/printk.c to a separate directory and
got warned about docproc.c not finding this file anymore.
These entries seem very arbitrary.
(Also, I've never seen, nor cared about, them before)
Any way to autogenerate this .tmpl file?
next parent reply other threads:[~2013-07-19 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51e89d4a.EzMm4kY3e/JyyINM%akpm@linux-foundation.org>
2013-07-19 2:07 ` Joe Perches [this message]
2013-07-19 5:42 ` docproc.c: Johannes Berg
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=1374199649.1949.143.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rob@landley.net \
/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
all inboxes | Powered by JetHome®