linux-kernel - docbook: fix fatal error in linux/input.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20101026114555.4b79977d.rdunlap@xenotime.net>
Date:	Tue, 26 Oct 2010 11:45:55 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	lkml <linux-kernel@...r.kernel.org>
Cc:	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: docbook: fix fatal error in linux/input.h

Hi,

Recent commit 8613e4c2872a87cc309a42de2c7091744dc54d0e:
Author: Mauro Carvalho Chehab <mchehab@...hat.com>
Date:   Thu Sep 9 21:54:22 2010 -0700
    Input: add support for large scancodes

causes a fatal error in docbook generation:

linux-2.6.36-git8/DOC1/Documentation/DocBook/device-drivers.xml:40690: parser error : StartTag: invalid element name
#define INPUT_KEYMAP_BY_INDEX	(1 << 0)
                             	    ^

I think that this message comes from xsltproc, but I'm not positive about that.
I also don't know of a really good fix for it.  However, I did find 2 ways to
work around the error:

a/ move the #define value to after the end of the struct input_keymap_entry, like:

/* flags bits: */
#define INPUT_KEYMAP_BY_INDEX	(1 << 0)

or
b/ don't use the "<< 0" (can leave the #define where it is in this case):
#define INPUT_KEYMAP_BY_INDEX	(1)

I have tested both of these patches and they work OK.
Are you OK with either of them?  or want to choose one?

thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/