From: Alan Stern <stern@rowland.harvard.edu>
To: Alex Elder <elder@linaro.org>
Cc: gregkh@linuxfoundation.org, 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
Subject: Re: [PATCH v2 1/3] usb: host: remove ehci-msm.c
Date: Thu, 26 Oct 2017 11:06:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1710261105090.1365-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20171026134827.615-2-elder@linaro.org>
On Thu, 26 Oct 2017, Alex Elder wrote:
> No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it.
What about old Qualcomm SoCs? What should they use instead?
Alan Stern
WARNING: multiple messages have this Message-ID (diff)
From: Alan Stern <stern@rowland.harvard.edu>
To: Alex Elder <elder@linaro.org>
Cc: gregkh@linuxfoundation.org, <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>
Subject: Re: [PATCH v2 1/3] usb: host: remove ehci-msm.c
Date: Thu, 26 Oct 2017 11:06:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1710261105090.1365-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20171026134827.615-2-elder@linaro.org>
On Thu, 26 Oct 2017, Alex Elder wrote:
> No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it.
What about old Qualcomm SoCs? What should they use instead?
Alan Stern
WARNING: multiple messages have this Message-ID (diff)
From: stern@rowland.harvard.edu (Alan Stern)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] usb: host: remove ehci-msm.c
Date: Thu, 26 Oct 2017 11:06:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1710261105090.1365-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20171026134827.615-2-elder@linaro.org>
On Thu, 26 Oct 2017, Alex Elder wrote:
> No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it.
What about old Qualcomm SoCs? What should they use instead?
Alan Stern
next prev parent reply other threads:[~2017-10-26 15:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 13:48 [PATCH v2 0/3] usb: remove some unused code Alex Elder
2017-10-26 13:48 ` Alex Elder
2017-10-26 13:48 ` [PATCH v2 1/3] usb: host: remove ehci-msm.c Alex Elder
2017-10-26 13:48 ` Alex Elder
2017-10-26 15:06 ` Alan Stern [this message]
2017-10-26 15:06 ` Alan Stern
2017-10-26 15:06 ` Alan Stern
2017-10-30 21:06 ` Bjorn Andersson
2017-10-30 21:06 ` Bjorn Andersson
2017-10-26 13:48 ` [PATCH v2 2/3] usb: phy: remove phy-msm-usb.c Alex Elder
2017-10-26 13:48 ` Alex Elder
2017-10-26 13:48 ` [PATCH v2 3/3] usb: phy: remove phy-qcom-8x16-usb.c Alex Elder
2017-10-26 13:48 ` Alex Elder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44L0.1710261105090.1365-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=Linyu.Yuan@alcatel-sbell.com.cn \
--cc=andy.gross@linaro.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=elder@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=manjunath.goudar@linaro.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.