linux-kernel - Re: [PATCH] HID: Fix the Kconfig option for generic device handling

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

Message-ID: <alpine.LNX.2.00.1206251726110.18612@pobox.suse.cz>
Date:	Mon, 25 Jun 2012 17:26:25 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Henrik Rydberg <rydberg@...omail.se>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jan Beulich <jbeulich@...e.com>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] HID: Fix the Kconfig option for generic device
 handling

On Mon, 25 Jun 2012, Henrik Rydberg wrote:

> > > The generic HID driver is obviously not a special driver, so move
> > > it outside of the special drivers menu. Explain the usage and make
> > > the default follow the HID setting. This should simplify migration
> > > from older kernels.
> > > 
> > > Reported-by: Jan Beulich <jbeulich@...e.com>
> > > Signed-off-by: Henrik Rydberg <rydberg@...omail.se>
> > > ---
> > > Hi Jiri,
> > > 
> > > As pointed out by Jan Beulich, the generic hid driver Kconfig option
> > > is confusing. This patch ought to fix most of the concerns. For 3.5.
> > 
> > The change makes sense. I'd however propose to perhaps unify 
> > CONFIG_HID_SUPPORT and CONFIG_HID, while we are at it ... ?
> 
> Here is a version putting together both patches sent previously, and in 
> addition removing the HID_SUPPORT option.

Applied, thank you Henrik.

-- 
Jiri Kosina
SUSE Labs
--
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/