From: Nick Fan <nick.fan@mediatek.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Nishanth Menon <nm@ti.com>,
Chiawen.Lee@mediatek.com, srv_heupstream@mediatek.com,
linux-pm@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
Viresh Kumar <vireshk@kernel.org>,
erin.lo@mediatek.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, tfiga@chromium.org,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] opp: Add API for getting voltage from supplies
Date: Fri, 14 Dec 2018 09:36:49 +0800 [thread overview]
Message-ID: <1544751409.6417.22.camel@mtksdaap41> (raw)
In-Reply-To: <20181213104247.kosguuoukoi645pf@vireshk-i7>
On Thu, 2018-12-13 at 16:12 +0530, Viresh Kumar wrote:
> On 13-12-18, 18:36, Nick Fan wrote:
> > This new API is suitable for the users that required to access for
> > multiple regulators. And I am one of users who uses this API, but I am
> > not able to upstream the GPU kernel driver which uses the new API.
>
> Look at it from mainline's perspective..
>
> - We don't (can't) care about non-mainline stuff. Actually we do care,
> but we can't add code to mainline which is not going to be used by
> any mainline user.
>
> - I am fine with introducing the new API, but that will happen only if
> there is going to be a mainline user as well.
>
> - As you are going to maintain your GPU driver offline, you can
> maintain this patch too.
>
> Sorry Nick.
>
It's OK.
I got your ideas.
Thanks a lot for the explanation and review on this patch.
--
Nick Fan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-12-14 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1543906760-15631-1-git-send-email-Nick.Fan@mediatek.com>
2018-12-04 8:21 ` [PATCH] opp: Add API for getting voltage from supplies Viresh Kumar
2018-12-10 12:36 ` Nick Fan
2018-12-13 6:38 ` Viresh Kumar
2018-12-13 10:36 ` Nick Fan
2018-12-13 10:42 ` Viresh Kumar
2018-12-14 1:36 ` Nick Fan [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=1544751409.6417.22.camel@mtksdaap41 \
--to=nick.fan@mediatek.com \
--cc=Chiawen.Lee@mediatek.com \
--cc=erin.lo@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@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