All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk <linux-clk@vger.kernel.org>
Subject: Re: [PATCH] clk: impd1: Look up clock-output-names
Date: Tue, 05 May 2020 12:13:08 -0700	[thread overview]
Message-ID: <158870598840.26370.15595608833504297253@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <CACRpkdbrkZnD8JpaWgqY6R4gAbsrBh2Xwfe+Nm15SEUPOJnfEA@mail.gmail.com>

Quoting Linus Walleij (2020-05-05 01:06:16)
> On Tue, May 5, 2020 at 8:23 AM Stephen Boyd <sboyd@kernel.org> wrote:
> > Quoting Linus Walleij (2020-04-28 05:51:10)
> > > On Wed, Apr 22, 2020 at 12:02 PM Stephen Boyd <sboyd@kernel.org> wrote:
> > > > Quoting Linus Walleij (2020-04-16 01:13:48)
> > > > > The IM-PD1 still need to pass the clock output names.
> > > > >
> > > > > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > > >
> > > > Is this a
> > > >
> > > > Fixes: 84655b762a27 ("clk: versatile: Add device tree probing for IM-PD1 clocks")
> > > >
> > > > change?
> > >
> > > Yep. Can you fold it in when applying?
> >
> > This is being deleted so does it matter anymore?
> 
> This patch is for the device tree path. What is getting deleted
> is the board file path, if I'm not mistaken.
> 

Ah ok! Thanks for clarifying.

  reply	other threads:[~2020-05-05 19:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  8:13 [PATCH] clk: impd1: Look up clock-output-names Linus Walleij
2020-04-22 10:02 ` Stephen Boyd
2020-04-28 12:51   ` Linus Walleij
2020-05-05  6:23     ` Stephen Boyd
2020-05-05  8:06       ` Linus Walleij
2020-05-05 19:13         ` Stephen Boyd [this message]
2020-05-05 19:13 ` Stephen Boyd

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=158870598840.26370.15595608833504297253@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.