From: James Hogan <james@albanarts.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux Input <linux-input@vger.kernel.org>,
linux-media@vger.kernel.org, Jarod Wilson <jarod@redhat.com>,
Maxim Levitsky <maximlevitsky@gmail.com>,
David Hardeman <david@hardeman.nu>, Jiri Kosina <jkosina@suse.cz>,
Ville Syrjala <syrjala@sci.fi>,
linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH 1/6] Input: add support for large scancodes
Date: Fri, 29 Oct 2010 23:34:15 +0100 [thread overview]
Message-ID: <201010292334.20732.james@albanarts.com> (raw)
In-Reply-To: <201010292236.07437.james@albanarts.com>
On Friday 29 October 2010 22:36:06 James Hogan wrote:
> I thought I better point out that this breaks make htmldocs (see below)
> because of the '<' characters "in" a kernel doc'd struct. This is with
> 12ba8d1e9262ce81a695795410bd9ee5c9407ba1 from Linus' tree (>2.6.36). Moving
> the #define below the struct works around the problem, but I guess the real
> issue is in the kerneldoc code.
appologies for the noise.
I see Randy had already beaten me to a fix.
Cheers
James
next prev parent reply other threads:[~2010-10-29 22:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 7:41 [PATCH 0/6] Large scancode handling Dmitry Torokhov
2010-09-08 7:41 ` [PATCH 1/6] Input: add support for large scancodes Dmitry Torokhov
2010-10-29 21:36 ` James Hogan
2010-10-29 22:34 ` James Hogan [this message]
2010-09-08 7:41 ` [PATCH 2/6] Input: sparse-keymap - switch to using new keycode interface Dmitry Torokhov
2010-09-08 7:41 ` [PATCH 3/6] Input: hid-input " Dmitry Torokhov
2010-09-08 7:42 ` [PATCH 4/6] Input: winbond-cir " Dmitry Torokhov
2010-09-08 21:16 ` David Härdeman
2010-09-08 23:00 ` Dmitry Torokhov
2010-09-08 23:00 ` Dmitry Torokhov
2010-09-08 23:09 ` David Härdeman
2010-09-08 23:09 ` David Härdeman
2010-09-08 23:14 ` Mauro Carvalho Chehab
2010-09-08 23:14 ` Mauro Carvalho Chehab
2010-09-08 7:42 ` [PATCH 5/6] Input: ati-remote2 " Dmitry Torokhov
2010-09-09 12:40 ` Ville Syrjälä
2010-09-13 16:28 ` Dmitry Torokhov
2010-09-13 16:28 ` Dmitry Torokhov
2010-09-15 21:04 ` Ville Syrjälä
2010-09-15 21:04 ` Ville Syrjälä
2010-09-15 21:13 ` Dmitry Torokhov
2010-09-08 7:42 ` [PATCH 6/6] Input: media/IR " Dmitry Torokhov
2010-09-08 9:48 ` [PATCH 0/6] Large scancode handling Jiri Kosina
2010-09-08 14:24 ` Jarod Wilson
2010-09-08 15:15 ` Mauro Carvalho Chehab
2010-09-08 15:22 ` Jarod Wilson
2010-09-08 15:25 ` Jiri Kosina
2010-09-08 15:36 ` Dmitry Torokhov
2010-09-08 16:09 ` Jarod Wilson
2010-09-08 16:56 ` Dmitry Torokhov
2010-09-08 17:29 ` Jarod Wilson
2010-09-13 15:00 ` Jiri Kosina
2010-09-08 15:36 ` Dmitry Torokhov
2010-09-08 14:31 ` Jarod Wilson
2010-09-08 15:34 ` Dmitry Torokhov
2010-09-13 17:48 ` Jarod Wilson
2010-09-14 1:26 ` Dmitry Torokhov
2010-09-08 15:23 ` Mauro Carvalho Chehab
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=201010292334.20732.james@albanarts.com \
--to=james@albanarts.com \
--cc=david@hardeman.nu \
--cc=dmitry.torokhov@gmail.com \
--cc=jarod@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=mchehab@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=syrjala@sci.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.