public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mike Turquette <mturquette@ti.com>
Cc: linux@arm.linux.org.uk, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	jeremy.kerr@canonical.com, broonie@opensource.wolfsonmicro.com,
	tglx@linutronix.de, linus.walleij@stericsson.com,
	amit.kucheria@linaro.org, dsaxena@linaro.org, patches@linaro.org,
	linaro-dev@lists.linaro.org, aul@pwsan.com,
	grant.likely@secretlab.ca, sboyd@quicinc.com,
	shawn.guo@freescale.com, skannan@quicinc.com,
	magnus.damm@gmail.com, arnd.bergmann@linaro.org,
	eric.miao@linaro.org, richard.zhao@linaro.org,
	Mike Turquette <mturquette@linaro.org>
Subject: Re: [PATCH v3 0/5] common clk framework
Date: Tue, 22 Nov 2011 07:42:59 -0800	[thread overview]
Message-ID: <20111122154259.GA18954@kroah.com> (raw)
In-Reply-To: <1321926047-14211-1-git-send-email-mturquette@linaro.org>

On Mon, Nov 21, 2011 at 05:40:42PM -0800, Mike Turquette wrote:
>   .sysfs support.  Visualize your clk tree at /sys/clk!  Where would be
> a better place to put the clk tree besides the root of /sys/?

Um, in the "proper" place for it under /sys/devices like the rest of the
device tree is?

> When a consensus on this is reached I'll submit the proper changes to
> Documentation/ABI/testing/.

I would like to see this documentation now, as it explains what you are
trying to do with the userspace api.

More comments on your sysfs patch...

thanks,

greg k-h

  parent reply	other threads:[~2011-11-22 15:49 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  1:40 [PATCH v3 0/5] common clk framework Mike Turquette
2011-11-22  1:40 ` [PATCH v3 1/5] clk: Kconfig: add entry for HAVE_CLK_PREPARE Mike Turquette
2011-11-26  0:51   ` Shawn Guo
2011-11-22  1:40 ` [PATCH v3 2/5] Documentation: common clk API Mike Turquette
2011-11-23  2:03   ` Saravana Kannan
2011-11-23 20:33     ` Turquette, Mike
2011-11-26  8:47       ` Shawn Guo
2011-11-27  1:43         ` Turquette, Mike
2011-11-22  1:40 ` [PATCH v3 3/5] clk: introduce the common clock framework Mike Turquette
2011-11-23  3:12   ` Saravana Kannan
2011-11-23 21:30     ` Turquette, Mike
2011-11-26 13:22   ` Shawn Guo
2011-11-27  6:00     ` Turquette, Mike
2011-12-01  1:20   ` Paul Walmsley
2011-12-01  5:53     ` Turquette, Mike
2011-12-01  6:39       ` Paul Walmsley
2011-12-01 14:42         ` Mark Brown
2011-12-01 18:25           ` Turquette, Mike
2011-12-01 18:30           ` Paul Walmsley
2011-12-01 18:32             ` Mark Brown
2011-12-01 22:03             ` Russell King - ARM Linux
2011-12-03  1:04               ` Paul Walmsley
2011-12-01  8:45     ` Russell King - ARM Linux
2011-12-02 17:13       ` Paul Walmsley
2011-12-02 20:23         ` Russell King - ARM Linux
2011-12-02 20:32           ` Uwe Kleine-König
2011-12-01  2:13   ` Paul Walmsley
2011-12-05 21:15   ` Paul Walmsley
2011-12-05 23:48     ` Russell King - ARM Linux
2011-12-06  1:37       ` Paul Walmsley
2011-12-06  6:28         ` Paul Walmsley
2011-12-05 23:40   ` Turquette, Mike
2011-11-22  1:40 ` [PATCH v3 4/5] clk: basic gateable and fixed-rate clks Mike Turquette
2011-11-22 13:11   ` Arnd Bergmann
2011-11-22 15:03     ` Mark Salter
2011-11-22 15:49       ` Arnd Bergmann
2011-11-26 13:48   ` Shawn Guo
2011-11-27  6:03     ` Turquette, Mike
2011-11-27  0:09   ` Shawn Guo
2011-11-22  1:40 ` [PATCH v3 5/5] clk: export tree topology and clk data via sysfs Mike Turquette
2011-11-22 13:07   ` Arnd Bergmann
2011-11-22 17:42     ` Mike Turquette
2011-11-22 15:49   ` Greg KH
2011-11-22 17:57     ` Mike Turquette
2011-11-22 19:13       ` Greg KH
2011-11-23  3:48         ` Saravana Kannan
2011-11-23 20:43           ` Turquette, Mike
2011-11-23 16:59         ` Tony Lindgren
2011-11-23 18:06           ` Russell King - ARM Linux
2011-11-23 18:55             ` Tony Lindgren
2011-11-23 19:09               ` Mark Brown
2011-11-23 19:19                 ` Tony Lindgren
2011-11-23 22:42               ` Russell King - ARM Linux
2011-11-24  1:08                 ` Tony Lindgren
     [not found]   ` <CACxGe6sOd6MiyYaok6BsihJtp-NNsm3WQf+aUPGMRFRpSLw2mQ@mail.gmail.com>
2011-11-22 18:01     ` Mike Turquette
2011-11-22 19:19       ` Grant Likely
2011-11-22 20:02         ` Arnd Bergmann
2011-11-22 20:19           ` Turquette, Mike
2011-11-22 15:42 ` Greg KH [this message]
2011-11-22 17:45   ` [PATCH v3 0/5] common clk framework Russell King - ARM Linux
2011-11-22 18:09     ` Mike Turquette
2011-11-22 19:12       ` Greg KH
2011-11-22 19:30         ` Mark Brown
2011-11-26  7:06 ` Shawn Guo
2011-11-27  1:12   ` Turquette, Mike

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=20111122154259.GA18954@kroah.com \
    --to=greg@kroah.com \
    --cc=amit.kucheria@linaro.org \
    --cc=arnd.bergmann@linaro.org \
    --cc=aul@pwsan.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dsaxena@linaro.org \
    --cc=eric.miao@linaro.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jeremy.kerr@canonical.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mturquette@linaro.org \
    --cc=mturquette@ti.com \
    --cc=patches@linaro.org \
    --cc=richard.zhao@linaro.org \
    --cc=sboyd@quicinc.com \
    --cc=shawn.guo@freescale.com \
    --cc=skannan@quicinc.com \
    --cc=tglx@linutronix.de \
    /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