From: Randy Dunlap <rdunlap@xenotime.net>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: docbook: fix fatal error in linux/input.h
Date: Tue, 26 Oct 2010 12:17:47 -0700 [thread overview]
Message-ID: <20101026121747.897eddc9.rdunlap@xenotime.net> (raw)
In-Reply-To: <4CC7283D.3010205@redhat.com>
On Tue, 26 Oct 2010 17:13:01 -0200 Mauro Carvalho Chehab wrote:
> Em 26-10-2010 16:45, Randy Dunlap escreveu:
> > Hi,
> >
> > Recent commit 8613e4c2872a87cc309a42de2c7091744dc54d0e:
> > Author: Mauro Carvalho Chehab <mchehab@redhat.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?
>
>
> Hmm... probably, the first one is not correct.
Why not? All it does is move the line to after the end of the struct.
> I suspect that the right way is to use something like:
>
> #define INPUT_KEYMAP_BY_INDEX (1 << 0)
>
> Could you please test if this would fix the issue?
You are suggesting putting that into include/linux/input.h ??
That would make sense if some tool converted "<<" to "<<".
And that may be where the problem is, but I don't know those tools.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-10-26 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 18:45 Randy Dunlap
2010-10-26 19:13 ` Mauro Carvalho Chehab
2010-10-26 19:17 ` Randy Dunlap [this message]
2010-10-26 20:08 ` Mauro Carvalho Chehab
2010-10-26 20:15 ` Mauro Carvalho Chehab
2010-10-26 20:51 ` Randy Dunlap
2010-10-26 20:59 ` Randy Dunlap
2010-10-26 21:07 ` Randy Dunlap
2010-10-26 21:32 ` Randy Dunlap
2010-10-26 21:41 ` Dmitry Torokhov
2010-10-26 21:58 ` Randy Dunlap
2010-10-29 17:56 ` [PATCH] scripts/kernel-doc: escape special characters for xml struct output 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=20101026121747.897eddc9.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
/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®