From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Abel Vesa <abel.vesa@nxp.com>,
Carlo Caione <ccaione@baylibre.com>,
linux-imx@nxp.com, kernel@pengutronix.de,
Lucas Stach <l.stach@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Bai Ping <ping.bai@nxp.com>
Subject: Re: [PATCH] clk: imx8mq: Add support for the CLKO1 clock
Date: Thu, 28 Feb 2019 10:15:12 +0800 [thread overview]
Message-ID: <20190228021509.GA26041@dragon> (raw)
In-Reply-To: <155078140414.77512.3157214123340597508@swboyd.mtv.corp.google.com>
On Thu, Feb 21, 2019 at 12:36:44PM -0800, Stephen Boyd wrote:
> Quoting Fabio Estevam (2019-01-30 16:20:56)
> > Add the entry for the CLKO1 clock.
> >
> > Signed-off-by: Fabio Estevam <festevam@gmail.com>
> > ---
>
> Applied to clk-next but I had to fix the whole DT binding number because
> I don't know what this patch is based on. In fact, please get everyone
> involved at NXP and whoever else is working on i.MX clk drivers to
> coordinate somehow. I just spent 20 minutes working through the set of
> imx patches in my inbox and I see approximately 6 different authors all
> sending out a few clks at a time for the same drivers with zero
> information about what the patches are based on or what order they're
> supposed to be applied in.
>
> If someone wants to collect all the patches and indicate on the list
> they've picked them up and will be sending them as a pull request that's
> fine.
I will help collect the i.MX platform clock patches and send you as
pull request.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-28 2:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 0:20 [PATCH] clk: imx8mq: Add support for the CLKO1 clock Fabio Estevam
2019-01-31 7:33 ` Abel Vesa
2019-02-21 20:36 ` Stephen Boyd
2019-02-22 1:07 ` Fabio Estevam
2019-02-22 4:43 ` Aisheng Dong
2019-02-28 2:15 ` Shawn Guo [this message]
2019-02-28 18:27 ` Stephen Boyd
2019-03-01 2:01 ` Shawn Guo
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=20190228021509.GA26041@dragon \
--to=shawnguo@kernel.org \
--cc=abel.vesa@nxp.com \
--cc=ccaione@baylibre.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=ping.bai@nxp.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).