From: Jeffrey Hugo <jhugo@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>, mturquette@baylibre.com
Cc: bjorn.andersson@linaro.org, georgi.djakov@linaro.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] clk: Probe defer clk_get() on orphans
Date: Thu, 21 Mar 2019 08:50:43 -0600 [thread overview]
Message-ID: <29112c43-790e-e7e4-9e4b-9eda8f5bdb78@codeaurora.org> (raw)
In-Reply-To: <155191438574.20095.6161802248500300707@swboyd.mtv.corp.google.com>
On 3/6/2019 4:19 PM, Stephen Boyd wrote:
> Quoting Jeffrey Hugo (2019-03-06 13:48:13)
>> Ping?
>>
>> Stephen, I know as this depends on your clock parent handling series
>> (happens to apply just fine to v2), its not going to be accepted until
>> that gets sorted out, but do you have any thoughts on if this seems like
>> an appropriate thing to do, or if you'd like to see a different solution?
>
> Please don't ping during the merge window. I'll probably look at this
> patch next week.
>
Sorry about pinging during the merge window. At the time, I just
realized the patch has been on list for several weeks with no response,
but hadn't connected the dots that it happened to be the merge window at
that particular moment.
Any update on when you think you might get around to having a look at this?
--
Jeffrey Hugo
Qualcomm Datacenter Technologies as an affiliate of Qualcomm
Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2019-03-21 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 18:57 [PATCH v1] clk: Probe defer clk_get() on orphans Jeffrey Hugo
2019-03-06 21:48 ` Jeffrey Hugo
2019-03-06 23:19 ` Stephen Boyd
2019-03-21 14:50 ` Jeffrey Hugo [this message]
2019-04-05 14:34 ` Jeffrey Hugo
2019-04-23 0:52 ` Stephen Boyd
2019-04-30 20:52 ` Jeffrey Hugo
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=29112c43-790e-e7e4-9e4b-9eda8f5bdb78@codeaurora.org \
--to=jhugo@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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).