From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Kosina Date: Mon, 22 Mar 2010 08:56:38 +0000 Subject: Re: [PATCH v2 2/6] hid: add framebuffer support to PicoLCD device Message-Id: List-Id: References: <20100320170014.440959a8@neptune.home> <20100320170415.6ee219c8@neptune.home> <45a44e481003210024l2c66938fp9436d34f6473f811@mail.gmail.com> <20100321171128.324a606f@neptune.home> In-Reply-To: <20100321171128.324a606f@neptune.home> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: =?ISO-8859-15?Q?Bruno_Pr=E9mont?= Cc: Jaya Kumar , linux-input@vger.kernel.org, linux-usb@vger.kernel.org, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, "Rick L. Vinyard Jr." , Nicu Pavel , Oliver Neukum On Sun, 21 Mar 2010, Bruno Prémont wrote: > > > --- > > >  drivers/hid/Kconfig       |    7 +- > > >  drivers/hid/hid-picolcd.c |  454 +++++++++++++++++++++++++++++++++++++++++++++ > > >  2 files changed, 460 insertions(+), 1 deletions(-) > > > > It is customary for framebuffer drivers to live in drivers/video. This > > is the first one I've reviewed that is outside of it. Is there a good > > reason for this one to be outside of it? If so, could you put it in > > the comments. > > I've kept all the pieces of PicoLCD driver together under hid, > as it's a HID based device. Framebuffer is just one of its features and > keeping pieces together makes it easier to handle. I think it makes sense for a HID driver for this device to contain the framebuffer bits as well ... from user perspective, this seems to be HID device, with "extra" framebuffer display on it. If framebuffer folks Ack the fb-related code, I am fine keeping it under drivers/hid. Thanks, -- Jiri Kosina SUSE Labs, Novell Inc.