All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Peter De Schrijver
	<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH RESEND] clk: flatten clk tree in debugfs
Date: Thu, 26 Jun 2014 14:36:45 -0700	[thread overview]
Message-ID: <20140626213645.32686.26036@quantum> (raw)
In-Reply-To: <20140626163906.GI3679-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>

Quoting Peter De Schrijver (2014-06-26 09:39:06)
> On Fri, Jun 13, 2014 at 10:02:39AM +0200, Peter De Schrijver wrote:
> > On Fri, May 30, 2014 at 05:03:57PM +0200, Peter De Schrijver wrote:
> > > This patch flattens the clk tree in CCF debugfs. Instead of representing the
> > > clocks and their hierarchy as a directory structure under
> > > /sys/kernel/debug/clk, each clock gets a single directory directly under
> > > /sys/kernel/debug/clk. The orphans directory is replaced by a file called
> > > clk_orphan_summary.
> > 
> > Mike,
> > 
> > Any problems with this? What needs to be done to make this patch go forward?

Applied to clk-next.

Regards,
Mike

> > 
> 
> Do you think this could be merged for the 3.17?
> 
> Thanks,
> 
> Peter.

WARNING: multiple messages have this Message-ID (diff)
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] clk: flatten clk tree in debugfs
Date: Thu, 26 Jun 2014 14:36:45 -0700	[thread overview]
Message-ID: <20140626213645.32686.26036@quantum> (raw)
In-Reply-To: <20140626163906.GI3679@tbergstrom-lnx.Nvidia.com>

Quoting Peter De Schrijver (2014-06-26 09:39:06)
> On Fri, Jun 13, 2014 at 10:02:39AM +0200, Peter De Schrijver wrote:
> > On Fri, May 30, 2014 at 05:03:57PM +0200, Peter De Schrijver wrote:
> > > This patch flattens the clk tree in CCF debugfs. Instead of representing the
> > > clocks and their hierarchy as a directory structure under
> > > /sys/kernel/debug/clk, each clock gets a single directory directly under
> > > /sys/kernel/debug/clk. The orphans directory is replaced by a file called
> > > clk_orphan_summary.
> > 
> > Mike,
> > 
> > Any problems with this? What needs to be done to make this patch go forward?

Applied to clk-next.

Regards,
Mike

> > 
> 
> Do you think this could be merged for the 3.17?
> 
> Thanks,
> 
> Peter.

WARNING: multiple messages have this Message-ID (diff)
From: Mike Turquette <mturquette@linaro.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] clk: flatten clk tree in debugfs
Date: Thu, 26 Jun 2014 14:36:45 -0700	[thread overview]
Message-ID: <20140626213645.32686.26036@quantum> (raw)
In-Reply-To: <20140626163906.GI3679@tbergstrom-lnx.Nvidia.com>

Quoting Peter De Schrijver (2014-06-26 09:39:06)
> On Fri, Jun 13, 2014 at 10:02:39AM +0200, Peter De Schrijver wrote:
> > On Fri, May 30, 2014 at 05:03:57PM +0200, Peter De Schrijver wrote:
> > > This patch flattens the clk tree in CCF debugfs. Instead of representing the
> > > clocks and their hierarchy as a directory structure under
> > > /sys/kernel/debug/clk, each clock gets a single directory directly under
> > > /sys/kernel/debug/clk. The orphans directory is replaced by a file called
> > > clk_orphan_summary.
> > 
> > Mike,
> > 
> > Any problems with this? What needs to be done to make this patch go forward?

Applied to clk-next.

Regards,
Mike

> > 
> 
> Do you think this could be merged for the 3.17?
> 
> Thanks,
> 
> Peter.

  parent reply	other threads:[~2014-06-26 21:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 15:03 [PATCH RESEND] clk: flatten clk tree in debugfs Peter De Schrijver
2014-05-30 15:03 ` Peter De Schrijver
2014-05-30 15:03 ` Peter De Schrijver
     [not found] ` <1401462237-14954-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-06-13  8:02   ` Peter De Schrijver
2014-06-13  8:02     ` Peter De Schrijver
2014-06-13  8:02     ` Peter De Schrijver
2014-06-26 16:39     ` Peter De Schrijver
2014-06-26 16:39       ` Peter De Schrijver
     [not found]       ` <20140626163906.GI3679-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2014-06-26 21:36         ` Mike Turquette [this message]
2014-06-26 21:36           ` Mike Turquette
2014-06-26 21:36           ` Mike Turquette
2014-06-27  7:29           ` Peter De Schrijver
2014-06-27  7:29             ` Peter De Schrijver
2014-06-27  7:29             ` Peter De Schrijver
2014-06-27  7:31           ` Peter De Schrijver
2014-06-27  7:31             ` Peter De Schrijver
2014-06-27  7:31             ` Peter De Schrijver

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=20140626213645.32686.26036@quantum \
    --to=mturquette-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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 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.