From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: xuwei5@hisilicon.com, Arnd Bergmann <arnd@arndb.de>,
Stephen Boyd <sboyd@codeaurora.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
"open list:OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/HISILICON SOC..."
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V4] ARM64: dts: hi6220-hikey: Add clock binding for the pmic mfd
Date: Fri, 5 May 2017 10:32:28 +0200 [thread overview]
Message-ID: <20170505083228.GC5252@mai> (raw)
In-Reply-To: <20170505074821.fgnkq6lggde6gdv2@dell>
On Fri, May 05, 2017 at 08:48:21AM +0100, Lee Jones wrote:
> On Fri, 05 May 2017, Daniel Lezcano wrote:
>
> > On Mon, Apr 24, 2017 at 10:40:22PM +0200, Daniel Lezcano wrote:
> > > The hi655x PMIC provides the regulators but also a clock. The latter is missing
> > > in the definition and in the DT, thus it is no possible to enable the WiFi which
> > > depends on this clock.
> > >
> > > The hi655x's clock has been added and the hi655x multifunction driver has
> > > updated with a clock-cell.
> > >
> > > This patch adds the clock-cells for the PMIC in the DT and updates the
> > > documentation.
> > >
> > > Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> > > Acked-by: Rob Herring <robh@kernel.org>
> > > Acked-by: Lee Jones <lee.jones@linaro.org>
> > > Cc: Arnd Bergmann <arnd@arndb.de>
> > > Cc: Stephen Boyd <sboyd@codeaurora.org>
> > > Cc: Michael Turquette <mturquette@baylibre.com>
> > > ---
> > > Changelog:
> > > v4:
> > > - Added Acked-by's
> > > - Updated the commit message with a better description
> > > ---
> >
> > Hi Xu Wei,
> >
> > a gentle reminder for this patch. Is it ok for you?
>
> a) Pings aren't usually received well. If you wish to remind
> maintainers of a patch's existence a [RESEND] is usually the most
> accepted method.
> b) There is usually little point (at least it's significantly reduced)
> in sending pings/resends whilst the merge-window is open. Maintainers
> usually take this time to take a little breather (rest) from their
> duties.
This patch is the last one of a series which was already merged. As the
series has been resend and split with a different submission path, I just
wanted to make sure there were no confusion.
The sentence "a gentle reminder" is clumsy.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2017-05-05 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 20:40 [PATCH V4] ARM64: dts: hi6220-hikey: Add clock binding for the pmic mfd Daniel Lezcano
2017-05-04 22:07 ` Daniel Lezcano
2017-05-05 7:48 ` Lee Jones
2017-05-05 8:32 ` Daniel Lezcano [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=20170505083228.GC5252@mai \
--to=daniel.lezcano@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox