linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "A.s. Dong" <aisheng.dong@nxp.com>
To: "thor.thayer@linux.intel.com" <thor.thayer@linux.intel.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"sboyd@kernel.org" <sboyd@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"mturquette@baylibre.com" <mturquette@baylibre.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>,
	"hdegoede@redhat.com" <hdegoede@redhat.com>
Subject: RE: [PATCH V6 0/4] clk: new APIs to handle all available clocks
Date: Sat, 13 Oct 2018 13:33:54 +0000	[thread overview]
Message-ID: <AM0PR04MB4211DBDC8D0684442A927CE580E30@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM0PR04MB42119BD28DDB7826DEE577F180E60@AM0PR04MB4211.eurprd04.prod.outlook.com>

Ping

> -----Original Message-----
> From: A.s. Dong
> Sent: Monday, October 8, 2018 6:43 PM
> To: thor.thayer@linux.intel.com; linux-clk@vger.kernel.org; sboyd@kernel.org
> Cc: linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> mturquette@baylibre.com; shawnguo@kernel.org; dl-linux-imx
> <linux-imx@nxp.com>; hdegoede@redhat.com
> Subject: RE: [PATCH V6 0/4] clk: new APIs to handle all available clocks
> 
> Hi Stephen,
> 
> Gently ping again..
> 
> > > >
> > > Just checking on the status of this patch. The clock routines
> > > (patches
> > > 1-3) are useful for one of my drivers but if they aren't accepted or
> > > will take a long time to be accepted, I'll need to refactor my driver.
> > >
> >
> > Thanks for this information.
> >
> > Stephen,
> > Would you help to proceed this?
> >
> 
> Regards
> Dong Aisheng

      reply	other threads:[~2018-10-13 13:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31  4:45 [PATCH V6 0/4] clk: new APIs to handle all available clocks Dong Aisheng
2018-08-31  4:45 ` [PATCH V6 1/4] clk: bulk: add of_clk_bulk_get() Dong Aisheng
2018-10-16 22:44   ` Stephen Boyd
2018-08-31  4:45 ` [PATCH V6 2/4] clk: add new APIs to operate on all available clocks Dong Aisheng
2018-10-16 22:44   ` Stephen Boyd
2018-08-31  4:45 ` [PATCH V6 3/4] clk: add managed version of clk_bulk_get_all Dong Aisheng
2018-10-16 22:44   ` Stephen Boyd
2018-08-31  4:45 ` [PATCH V6 4/4] video: simplefb: switch to use clk_bulk API to simplify clock operations Dong Aisheng
2018-08-31 10:09   ` Hans de Goede
2018-09-06  3:22 ` [PATCH V6 0/4] clk: new APIs to handle all available clocks A.s. Dong
2018-09-16 13:24   ` A.s. Dong
2018-09-19 14:47     ` Thor Thayer
2018-09-20  2:14       ` A.s. Dong
2018-10-08 10:43         ` A.s. Dong
2018-10-13 13:33           ` A.s. Dong [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=AM0PR04MB4211DBDC8D0684442A927CE580E30@AM0PR04MB4211.eurprd04.prod.outlook.com \
    --to=aisheng.dong@nxp.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=thor.thayer@linux.intel.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).