linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: shawnguo@kernel.org, kernel@pengutronix.de, linux-imx@nxp.com,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Fabio Estevam <festevam@gmail.com>, Abel Vesa <abel.vesa@nxp.com>,
	Bai Ping <ping.bai@nxp.com>, Carlo Caione <ccaione@baylibre.com>,
	Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH] clk: imx8mq: Add support for the CLKO1 clock
Date: Thu, 21 Feb 2019 12:36:44 -0800	[thread overview]
Message-ID: <155078140414.77512.3157214123340597508@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20190131002056.12024-1-festevam@gmail.com>

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. Otherwise, I recommend working together to post a coherent patch
series that adds the things that everyone wants or working from a stable
baseline like an rc tag and letting me figure out how to do the merging.
Either way, it looks like if I ever get a patch for imx clk drivers that
doesn't have a cover letter or is just adding a few clks here and there
I'll have to assume it's the same story as always and just toss them
into a clk-imx branch without a topic.


  parent reply	other threads:[~2019-02-21 20:36 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 [this message]
2019-02-22  1:07   ` Fabio Estevam
2019-02-22  4:43   ` Aisheng Dong
2019-02-28  2:15   ` Shawn Guo
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=155078140414.77512.3157214123340597508@swboyd.mtv.corp.google.com \
    --to=sboyd@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=shawnguo@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).