From: Randy Dunlap <randy.dunlap@oracle.com>
To: bbpetkov@yahoo.de
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [KERNEL-DOC] kill warnings when building mandocs
Date: Wed, 25 Apr 2007 13:22:45 -0700 [thread overview]
Message-ID: <20070425132245.01a1c6c4.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070420060250.GB3967@gollum.tnic>
On Fri, 20 Apr 2007 08:02:50 +0200 Borislav Petkov wrote:
> > > > Are other people seeing these warning messages ??
> > > Hm, is anyone building the manpages target at all?
> >
> > Other than the 2 of us... I couldn't say.
>
> By the way, can we consider the item
> "- clean up Documentation/DocBook/, fix warnings that occur on make *docs."
> from the KJ TODO list as now done?
OK, although a few of them may not be fixed until soon after 2.6.21
is released and pending patches are applied.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-04-25 20:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 9:14 Borislav Petkov
2007-04-13 9:29 ` Borislav Petkov
2007-04-18 17:16 ` Randy Dunlap
2007-04-19 6:30 ` Borislav Petkov
2007-04-19 7:19 ` [PATCHv2] " Borislav Petkov
2007-04-19 16:21 ` Randy Dunlap
2007-04-20 5:59 ` Borislav Petkov
2007-04-21 7:20 ` Andrew Morton
2007-04-22 7:40 ` [PATCHv3] " Borislav Petkov
2007-04-22 7:49 ` [PATCHv3] [KERNEL-DOC] kill warnings when building mandocs (fixed whitespaces) Borislav Petkov
2007-04-22 15:59 ` [PATCHv4] [KERNEL-DOC] kill warnings when building mandocs (final) Borislav Petkov
2007-04-14 16:13 ` [PATCH] [KERNEL-DOC] kill warnings when building mandocs Randy Dunlap
2007-04-15 7:10 ` Borislav Petkov
2007-04-17 10:49 ` Borislav Petkov
2007-04-18 16:03 ` Randy Dunlap
2007-04-19 6:20 ` Borislav Petkov
2007-04-19 15:53 ` Randy Dunlap
2007-04-20 6:02 ` Borislav Petkov
2007-04-25 20:22 ` Randy Dunlap [this message]
2007-04-22 23:04 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=20070425132245.01a1c6c4.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=bbpetkov@yahoo.de \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome