From: Heiko Stuebner <heiko@sntech.de>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Lin Huang <hl@rock-chips.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
Douglas Anderson <dianders@chromium.org>,
linux-rockchip@lists.infradead.org,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: rk3399: Add capacity-dmips-mhz attributes
Date: Sat, 02 Mar 2019 15:10:13 +0100 [thread overview]
Message-ID: <7233683.IuIR2UsBzk@phil> (raw)
In-Reply-To: <20190302131122.4d82da1b@why.wild-wind.fr.eu.org>
Am Samstag, 2. März 2019, 14:11:22 CET schrieb Marc Zyngier:
> On Sat, 2 Mar 2019 13:39:38 +0100
> Heiko Stuebner <heiko@sntech.de> wrote:
>
> Hi Heiko,
>
> > Hi Marc,
> >
> > Am Sonntag, 24. Februar 2019, 22:06:57 CET schrieb Marc Zyngier:
> > > On Sun, 24 Feb 2019 20:07:49 +0000
> > > Robin Murphy <robin.murphy@arm.com> wrote:
> >
> > [...]
> >
> > > > With the nits fixed,
> > > >
> > > > Tested-by: Robin Murphy <robin.murphy@arm.com>
> > >
> > > Cheers Robin. I'll post a v2 after -rc1.
> >
> > You can do that earlier as well, if you want to get it off your plate :-)
> > I'm normally not pausing patches over the merge-window, so from
> > my side there is no need to wait for rc1.
>
> Your wish is my command! ;-) v2 on its way.
that even worked without sudo :-P [0] ... I need to remember that
for when we run into each other the next time.
[0] https://xkcd.com/149/
_______________________________________________
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:[~2019-03-02 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 14:35 [PATCH] arm64: rk3399: Add capacity-dmips-mhz attributes Marc Zyngier
2019-02-24 20:07 ` Robin Murphy
2019-02-24 21:06 ` Marc Zyngier
2019-03-02 12:39 ` Heiko Stuebner
2019-03-02 13:11 ` Marc Zyngier
2019-03-02 14:10 ` Heiko Stuebner [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=7233683.IuIR2UsBzk@phil \
--to=heiko@sntech.de \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).