From: Stephen Boyd <sboyd@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
kevin-cw.chen@mediatek.com, mars.cheng@mediatek.com,
matthias.bgg@kernel.org, mturquette@baylibre.com
Cc: Matthias Brugger <mbrugger@suse.com>,
sean.wang@mediatek.com, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org, jasu@njomotys.info,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/3] Mark clocks as critical for MT6797
Date: Tue, 26 Feb 2019 09:53:09 -0800 [thread overview]
Message-ID: <155120358914.260864.17734674975447226263@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <f7ed0750-665a-76bc-df1a-95af39fef8ec@gmail.com>
Quoting Matthias Brugger (2019-02-26 04:59:44)
>
>
> On 14/02/2019 17:30, matthias.bgg@kernel.org wrote:
> > From: Matthias Brugger <mbrugger@suse.com>
> >
> > Jasper send this series some month ago. As there was no reaction from
> > his side, I'll do a friendly take-over.
> > I tested the patches on my Helios X20 boards and they fix the issue.
> > I didn't add a Tested-by tag as I added my Signed-off-by.
> >
> > Changes since v3:
> > - add comments explaining why the clock muxer and gates are marked
> > as critical
> >
> > Changes since v2 (https://patchwork.kernel.org/patch/10686759/):
> > - axi_sel is not needed, drop CLK_IS_CRITICAL for it.
> > - update commit message
> > - add Acked-by from Mars
> >
> > Changes since v1:
> > - add a fixes tag.
> >
>
> Steven, Mike any comments on this?
>
I got patch #1 and #2 in my queue and they're not threaded properly as
replies to each other. I'll have to go dig out the last patch somehow,
but probably I can apply them now.
_______________________________________________
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-02-26 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 16:30 [PATCH v4 0/3] Mark clocks as critical for MT6797 matthias.bgg
2019-02-26 12:59 ` Matthias Brugger
2019-02-26 17:53 ` Stephen Boyd [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=155120358914.260864.17734674975447226263@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=jasu@njomotys.info \
--cc=kevin-cw.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mars.cheng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=matthias.bgg@kernel.org \
--cc=mbrugger@suse.com \
--cc=mturquette@baylibre.com \
--cc=sean.wang@mediatek.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).