Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755860Ab2FYP0e (ORCPT ); Mon, 25 Jun 2012 11:26:34 -0400 Received: from cantor2.suse.de ([195.135.220.15]:51630 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752361Ab2FYP0d (ORCPT ); Mon, 25 Jun 2012 11:26:33 -0400 Date: Mon, 25 Jun 2012 17:26:25 +0200 (CEST) From: Jiri Kosina To: Henrik Rydberg Cc: Dmitry Torokhov , Jan Beulich , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] HID: Fix the Kconfig option for generic device handling In-Reply-To: <20120625151615.GA11770@polaris.bitmath.org> Message-ID: References: <1340356390-4614-1-git-send-email-rydberg@euromail.se> <20120625151615.GA11770@polaris.bitmath.org> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1143 Lines: 31 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 > > > Signed-off-by: Henrik Rydberg > > > --- > > > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/