From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933046AbdKCNJQ (ORCPT ); Fri, 3 Nov 2017 09:09:16 -0400 Received: from mail-io0-f195.google.com ([209.85.223.195]:55632 "EHLO mail-io0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756012AbdKCNJN (ORCPT ); Fri, 3 Nov 2017 09:09:13 -0400 X-Google-Smtp-Source: ABhQp+TZHF9WqS13+1bAZmdiIj15DwDvfgkIvtyvl9jW3Rj9RxusUS/deaJxzwWmqYwNUY6kNjj9jg== Subject: Re: [PATCH v3 2/3] usb: phy: remove phy-msm-usb.c To: Jack Pham , Alex Elder Cc: gregkh@linuxfoundation.org, stern@rowland.harvard.edu, balbi@kernel.org, manjunath.goudar@linaro.org, bjorn.andersson@linaro.org, Linyu.Yuan@alcatel-sbell.com.cn, andy.gross@linaro.org, tony@atomide.com, linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org References: <20171031131131.8099-1-elder@linaro.org> <20171031131131.8099-3-elder@linaro.org> <20171103000257.GG12812@usblab-sd-06.qualcomm.com> From: Alex Elder Message-ID: <5210a424-a4bb-b42f-1f17-074d2b4d58a7@ieee.org> Date: Fri, 3 Nov 2017 08:09:10 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171103000257.GG12812@usblab-sd-06.qualcomm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/02/2017 07:02 PM, Jack Pham wrote: > Hi Alex, > > On Tue, Oct 31, 2017 at 08:11:30AM -0500, Alex Elder wrote: >> No Qualcomm SoC requires the "phy-msm-usb.c" USB phy driver support >> any more, so remove the code. >> >> Suggested-by: Stephen Boyd >> Signed-off-by: Alex Elder >> Acked-by: Bjorn Andersson >> Acked-by: Andy Gross >> --- > > >> -#include > > This file and ehci-msm.c were the last consumers of this header, so it > too can now be deleted. Has your series been picked up yet? If so I or > someone can send a follow-up patch. Thanks for pointing that out! I'll post a new patch now to remove it. -Alex > > Jack >