linux-kernel - Re: [RFC: -mm patch] CONFIG_INPUT

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 30 Jan 2007 16:13:42 +0100
From:	Adrian Bunk <bunk@...sta.de>
To:	Jiri Kosina <jikos@...os.cz>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	linux-input@...ey.karlin.mff.cuni.cz
Subject: Re: [RFC: -mm patch] CONFIG_INPUT_DEBUG improvements

On Tue, Jan 30, 2007 at 04:07:04PM +0100, Jiri Kosina wrote:
> On Tue, 30 Jan 2007, Adrian Bunk wrote:
> 
> > This patch contains the following CONFIG_INPUT_DEBUG improvements:
> > - remove Makefile code for the nonexisting CONFIG_INPUT_DEBUG
> > - simpler Makefile for hid-debug.o
> > - replace all HID debug #define's with CONFIG_INPUT_DEBUG
> 
> Adrian,
> 
> thanks for the patch. In seems broken to me though (as I have written 
> accidentaly in different mail, so resending for mailinglists to get it) - 
> the option that should replace the legacy DEBUG macro should be 
> CONFIG_HID_DEBUG, not CONFIG_INPUT_DEBUG - your patch gets it right only 
> on some places.
>...

Thanks for the correction, these were copy'n'paste errors in my patch.

> Jiri Kosina

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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