From: Sricharan R <sricharan@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>,
agross@kernel.org, devicetree@vger.kernel.org,
linus.walleij@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-soc@vger.kernel.org, robh+dt@kernel.org,
sivaprak@codeaurora.org
Subject: Re: [PATCH 0/2] Add Global clock controller support for IPQ6018
Date: Mon, 6 Jan 2020 10:32:37 +0530 [thread overview]
Message-ID: <4b4b9f0b-5473-aea8-9ebb-7a2c4fecea07@codeaurora.org> (raw)
In-Reply-To: <20200105065919.4A548207FD@mail.kernel.org>
Hi Stephen,
On 1/5/2020 12:29 PM, Stephen Boyd wrote:
> Quoting Sricharan R (2020-01-03 03:25:42)
>> The IPQ6018 is Qualcomm\u2019s 802.11ax SoC for Routers,
>> Gateways and Access Points.
>>
>> This series adds Global clock controller support for ipq6018.
>
> Can you fold the fixes in?
>
Sure, will do and resend.
>>
>> The patches were a part of https://patchwork.kernel.org/cover/11303075/,
>> now moved it outside based on Stephen's suggestion.
>
> Thanks, but I still got the other pinctrl patches :(
>
ho, will remove you from CC on those.
Regards,
Sricharan
--
"QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2020-01-06 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 11:25 [PATCH 0/2] Add Global clock controller support for IPQ6018 Sricharan R
2020-01-03 11:25 ` [PATCH 1/2] clk: qcom: Add DT bindings for ipq6018 gcc clock controller Sricharan R
2020-01-05 6:59 ` [PATCH 0/2] Add Global clock controller support for IPQ6018 Stephen Boyd
2020-01-06 5:02 ` Sricharan R [this message]
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=4b4b9f0b-5473-aea8-9ebb-7a2c4fecea07@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sivaprak@codeaurora.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).