From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]:8258 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751467Ab0IHPP3 (ORCPT ); Wed, 8 Sep 2010 11:15:29 -0400 Message-ID: <4C87A87A.4060102@redhat.com> Date: Wed, 08 Sep 2010 12:15:06 -0300 From: Mauro Carvalho Chehab MIME-Version: 1.0 To: Jarod Wilson CC: Jiri Kosina , Dmitry Torokhov , Linux Input , linux-media@vger.kernel.org, Maxim Levitsky , David Hardeman , Ville Syrjala Subject: Re: [PATCH 0/6] Large scancode handling References: <20100908073233.32365.74621.stgit@hammer.corenet.prv> <20100908142418.GC22323@redhat.com> In-Reply-To: <20100908142418.GC22323@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-ID: Sender: Mauro Carvalho Chehab Em 08-09-2010 11:24, Jarod Wilson escreveu: > On Wed, Sep 08, 2010 at 11:48:50AM +0200, Jiri Kosina wrote: >> On Wed, 8 Sep 2010, Dmitry Torokhov wrote: >> >>> Hi Mauro, >>> >>> I guess I better get off my behind and commit the changes to support large >>> scancodes, or they will not make to 2.6.37 either... There isn't much >>> changes, except I followed David's suggestion and changed boolean index >>> field into u8 flags field. Still, please glance it over once again and >>> shout if you see something you do not like. >>> >>> Jiri, how do you want to handle the changes to HID? I could either push >>> them through my tree together with the first patch or you can push through >>> yours once the first change hits mainline. >> >> I think that there will unlikely be any conflict in .37 merge window in >> this area (and if there were, I'll sort it out). >> >> So please add >> >> Acked-by: Jiri Kosina >> >> to the hid-input.c bits and feel free to take it through your tree, if it >> is convenient for you. > > It'll conflict a little bith with the tivo slide patch I posted yesterday, > but mostly just minor context changes. I can redo that patch on top of > these changes if that's preferred. I can handle those context changes when merging the patches at linux-next and when merging upstream. We just need to sync in a way that Dmitry send his patch series before mine when sending them to Linus, and I'll take care of fixing the merge conflicts. Cheers, mauro.