From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, rusty@rustcorp.com.au
Subject: Re: [patch -mmotm] docbook: duplicate kernel-locking doc merge
Date: Tue, 27 May 2008 22:14:19 -0700 [thread overview]
Message-ID: <20080527221419.2f5ca991.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080527221327.dfcb4fb6.randy.dunlap@oracle.com>
On Tue, 27 May 2008 22:13:27 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Removed duplicated patch lines.
>
> I was checking mmotm (2008-0527) kernel docs and got this error:
>
> xmlto: input does not validate (status 3)
> /local/linsrc/mmotm-2008-0527-0032/Documentation/DocBook/kernel-locking.xml:722: element chapter: validity error : ID trylock-functions already defined
> <chapter id="trylock-functions">
> ^
> /local/linsrc/mmotm-2008-0527-0032/Documentation/DocBook/kernel-locking.xml:722: element chapter: validity error : ID trylock-functions already defined
> Document /local/linsrc/mmotm-2008-0527-0032/Documentation/DocBook/kernel-locking.xml does not validate
> make[1]: *** [Documentation/DocBook/kernel-locking.html] Error 3
> make[1]: *** Waiting for unfinished jobs....
> make: *** [htmldocs] Error 2
>
> Looks like Rusty's doc additions were duplicated.
ah, thanks, that's me trying to pick up patches which aren't in linux-next
yet. I normally don't bother doing that unless there's a lot of material
involved.
I'll zap the erroneously-included
rusty-misc-doc_add_a_chapter_about_trylock_functions_bug_9011.patch
next prev parent reply other threads:[~2008-05-28 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 5:13 [patch -mmotm] docbook: duplicate kernel-locking doc merge Randy Dunlap
2008-05-28 5:14 ` Andrew Morton [this message]
2008-05-29 8:08 ` Rusty Russell
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=20080527221419.2f5ca991.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rusty@rustcorp.com.au \
/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