From: Sandeep Maheswaram <quic_c_sanm@quicinc.com>
To: Stephen Boyd <swboyd@chromium.org>,
Andy Gross <agross@kernel.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
Doug Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
Rob Herring <robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_pkondeti@quicinc.com>, <quic_ppratap@quicinc.com>
Subject: Re: [PATCH v2] arm64: qcom: sc7280: Move USB2 controller nodes from common dtsi to SKU1
Date: Mon, 10 Jan 2022 10:26:09 +0530 [thread overview]
Message-ID: <135e8171-c210-1f70-e26f-167f8fdfcc74@quicinc.com> (raw)
In-Reply-To: <e605c057-a7a4-657a-06ee-f872e13e116e@quicinc.com>
Hi Bjorn,
On 12/15/2021 11:18 AM, Sandeep Maheswaram wrote:
> Hi Bjorn,
>
> On 12/3/2021 4:22 AM, Stephen Boyd wrote:
>> Quoting Sandeep Maheswaram (2021-12-01 21:17:28)
>>> Move USB2 controller and phy nodes from common dtsi file as it is
>>> required only for SKU1 board and change the mode to host mode as
>>> it will be used in host mode for SKU1.
>>>
>>> Signed-off-by: Sandeep Maheswaram <quic_c_sanm@quicinc.com>
>>> ---
>> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> Can you merge this change in qcom tree?
Is this patch merged in qcom tree ? If not can you please do so.
Regards
Sandeep
next prev parent reply other threads:[~2022-01-10 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 5:17 [PATCH v2] arm64: qcom: sc7280: Move USB2 controller nodes from common dtsi to SKU1 Sandeep Maheswaram
2021-12-02 15:46 ` Matthias Kaehlcke
2021-12-02 22:52 ` Stephen Boyd
2021-12-15 5:48 ` Sandeep Maheswaram
2022-01-10 4:56 ` Sandeep Maheswaram [this message]
2022-01-10 19:10 ` Bjorn Andersson
2022-01-31 18:24 ` (subset) " Bjorn Andersson
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=135e8171-c210-1f70-e26f-167f8fdfcc74@quicinc.com \
--to=quic_c_sanm@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mka@chromium.org \
--cc=quic_pkondeti@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).