From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: input.agent bits parse bug
Date: Fri, 26 Mar 2004 23:11:05 +0000 [thread overview]
Message-ID: <20040326231104.GI31372@kroah.com> (raw)
In-Reply-To: <87wu5o7h35.wl@ukai.org>
On Sun, Mar 14, 2004 at 03:11:10AM +0900, Fumitoshi UKAI wrote:
> Hi,
>
> Recent version of input.agent has some problems parsing modules.inputmap.
> From module-init-tools's code, modules.inputmap will have the following
> format
>
> name number of unsigned int
> evBits 1
> keyBits 16
> relBits 1
>
> absBits 2
> mscBits 1
> ledBits 1
> sndBits 1
> ffBits 4
>
> for each unsigned int value, it is printed by using format string "%lx"
> concatinated by ':'
>
> So, keyBits, absBits and ffBits can't be parsed as $(($<n>)) since it
> is not simple integer. And other bits parameter should be parsed as
> $((0x$<n>)) instead of $(($<n>)) because it is not decimal, but hex value.
>
> I think input.agent should be fixed as follows:
You already fixed this in cvs, by using input_match_bits(), right?
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-03-26 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 18:11 input.agent bits parse bug Fumitoshi UKAI
2004-03-26 23:11 ` Greg KH [this message]
2004-03-27 7:40 ` Fumitoshi UKAI
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=20040326231104.GI31372@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).