From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750903AbbFLE1o (ORCPT ); Fri, 12 Jun 2015 00:27:44 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:36047 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750722AbbFLE1m (ORCPT ); Fri, 12 Jun 2015 00:27:42 -0400 Date: Thu, 11 Jun 2015 21:27:41 -0700 From: Greg KH To: Chanwoo Choi Cc: balbi@ti.com, myungjoo.ham@samsung.com, k.kozlowski@samsung.com, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Subject: Re: [PATCH] extcon: Redefine the unique id of supported external connectors without 'enum extcon' type Message-ID: <20150612042741.GA10691@kroah.com> References: <1434075006-2931-1-git-send-email-cw00.choi@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1434075006-2931-1-git-send-email-cw00.choi@samsung.com> User-Agent: Mutt/1.5.23+89 (0255b37be491) (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 12, 2015 at 11:10:06AM +0900, Chanwoo Choi wrote: > This patch just redefine the unique id of supported external connectors without > 'enum extcon' type. Because unique id would be used on devictree file(*.dts) to > indicate the specific external connectors like key number of input framework. > So, I have the plan to move this definitions to following header file which > includes the unique id of supported external connectors. > - include/dt-bindings/extcon/extcon.h > > Fixes: 2a9de9c0f08d ("extcon: Use the unique id for external connector instead of string") > Signed-off-by: Chanwoo Choi > --- > Dear Greg, > > I sent pull-request[1] of extcon for 4.2. This patch[2] in the pull-request[2] > includes the one issue about 'enum extcon'. The 'enum extcon' type is ambiguous > and not clear. So, if you possible, I hope you to pick this patch on char-misc > git repository. I don't understand, I took that pull request, right? What does that have to do with this patch? greg k-h