linux-kernel - Re: [PATCH 2/3 v2] lirc driver for Windows MCE IR transceivers

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 for Android: free password hash cracker in your pocket

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

Message-Id: <B103AC62-9068-437A-94B8-5B4BDBB4D38D@wilsonet.com>
Date:	Sun, 15 Nov 2009 01:55:31 -0500
From:	Jarod Wilson <jarod@...sonet.com>
To:	Stefan Lippers-Hollmann <s.L-H@....de>
Cc:	Jarod Wilson <jarod@...hat.com>, linux-kernel@...r.kernel.org,
	linux-input@...r.kernel.org, linux-media@...r.kernel.org,
	Janne Grunau <j@...nau.net>,
	Christoph Bartelmus <lirc@...telmus.de>
Subject: Re: [PATCH 2/3 v2] lirc driver for Windows MCE IR transceivers

On Nov 13, 2009, at 3:43 PM, Stefan Lippers-Hollmann wrote:

> Hi
> 
> Thank you for trying to get lirc mainline. Hoping that no real complaints 
> against it arise, what about submitting the tree to linux-next, so it gets 
> more testing exposure before the merge window opens for 2.6.33?

At the point, I'd be happy with getting into linux-next or even the staging tree.

> On Friday 13 November 2009, Jarod Wilson wrote:
>> lirc driver for Windows Media Center Ed. IR transceivers
> [...]
>> Index: b/drivers/input/lirc/Kconfig
>> ===================================================================
>> --- a/drivers/input/lirc/Kconfig
>> +++ b/drivers/input/lirc/Kconfig
>> @@ -11,6 +11,10 @@ menuconfig INPUT_LIRC
>> 
>> if INPUT_LIRC
>> 
>> -# Device-specific drivers go here
>> +config LIRC_MCEUSB
>> +	tristate "Windows Media Center Ed. USB IR Transceiver"
>> +	depends on LIRC_DEV && USB
> 
> You have obviously renamed LIRC_DEV to INPUT_LIRC just before the 
> submission, but missed to do so for the individual drivers which still 
> depend on LIRC_DEV and are therefore not selectable; the same applies to
> [PATCH 3/3 v2] lirc driver for SoundGraph iMON IR receivers and displays.

D'oh. Yeah, I sure did. Didn't notice the fubar, because I was building and testing the stuff on an existing kernel that already had LIRC_DEV defined. Earlier versions actually had both INPUT_LIRC and LIRC_DEV, which are essentially one in the same. I'll fix that shortly.

-- 
Jarod Wilson
jarod@...sonet.com



--
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/