linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Dinh Nguyen <dinguyen@kernel.org>, Jerome Brunet <jbrunet@baylibre.com>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	Michael Turquette <mturquette@baylibre.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [PATCH] clk: socfpga: Don't have get_parent for single parent ops
Date: Wed, 05 Dec 2018 07:55:16 -0800	[thread overview]
Message-ID: <154402531604.88331.12202256691796911096@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <266a0a5d-5dfe-0e1c-276f-65163f1cef1b@kernel.org>

Quoting Dinh Nguyen (2018-12-05 07:17:41)
> Hi Stephen,
> 
> On 12/5/18 1:17 AM, Stephen Boyd wrote:
> > (Adding Dinh's korg email)
> > 
> > I also wonder if this driver is even used anymore or maybe we can delete
> > it?
> > 
> 
> The armv7 SoCFPGA platforms are using this driver.
> 

Ok and those platforms are booting in kernelci.org as
https://kernelci.org/boot/socfpga_cyclone5_de0_sockit/ perhaps?


  reply	other threads:[~2018-12-05 15:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 16:32 [PATCH] Revert "clk: fix __clk_init_parent() for single parent clocks" Jerome Brunet
2018-12-04 18:05 ` Stephen Boyd
2018-12-04 19:51   ` Jerome Brunet
2018-12-05  7:54     ` Stephen Boyd
2018-12-05 17:20       ` Jerome Brunet
2018-12-06 22:08         ` Stephen Boyd
2018-12-07 10:03           ` Jerome Brunet
2018-12-18  1:54             ` Stephen Boyd
2018-12-21 16:03               ` Jerome Brunet
2018-12-21 22:24                 ` Stephen Boyd
2018-12-04 19:34 ` [PATCH] clk: socfpga: Don't have get_parent for single parent ops Stephen Boyd
2018-12-05  7:17   ` Stephen Boyd
2018-12-05 15:17     ` Dinh Nguyen
2018-12-05 15:55       ` Stephen Boyd [this message]
2018-12-06 15:16         ` Dinh Nguyen
2018-12-18  1:54           ` Stephen Boyd
2018-12-18 15:48             ` Dinh Nguyen

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=154402531604.88331.12202256691796911096@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=yamada.masahiro@socionext.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).