All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajendra Nayak <rnayak@ti.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Mike Turquette <mturquette@ti.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	aletes.xgr@gmail.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Archit Taneja <archit@ti.com>, loml <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	"Cousson, Benoit" <b-cousson@ti.com>
Subject: Re: [PATCH] clk: fix compile for OF && !COMMON_CLK
Date: Tue, 17 Jul 2012 19:04:13 +0530	[thread overview]
Message-ID: <500569D5.3020508@ti.com> (raw)
In-Reply-To: <50056648.6000906@ti.com>

On Tuesday 17 July 2012 06:49 PM, Rajendra Nayak wrote:
> struct clk *clk_get(struct device *dev, const char *con_id)
> {
>          const char *dev_id = dev ? dev_name(dev) : NULL;
>          struct clk *clk;
>
>          if (dev) {
> ---->
>      Any reason why this isn't
>      if (dev->of_node) {
> ---->

Or rather,
	if (dev && dev->of_node) {
as Archit just pointed out to me.

WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: fix compile for OF && !COMMON_CLK
Date: Tue, 17 Jul 2012 19:04:13 +0530	[thread overview]
Message-ID: <500569D5.3020508@ti.com> (raw)
In-Reply-To: <50056648.6000906@ti.com>

On Tuesday 17 July 2012 06:49 PM, Rajendra Nayak wrote:
> struct clk *clk_get(struct device *dev, const char *con_id)
> {
>          const char *dev_id = dev ? dev_name(dev) : NULL;
>          struct clk *clk;
>
>          if (dev) {
> ---->
>      Any reason why this isn't
>      if (dev->of_node) {
> ---->

Or rather,
	if (dev && dev->of_node) {
as Archit just pointed out to me.

  reply	other threads:[~2012-07-17 13:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 21:46 [PATCH] clk: fix compile for OF && !COMMON_CLK Rob Herring
2012-07-16 21:46 ` Rob Herring
2012-07-17  0:12 ` Mike Turquette
2012-07-17  0:12   ` Mike Turquette
2012-07-17  2:08   ` Rob Herring
2012-07-17  2:08     ` Rob Herring
2012-07-17 13:19     ` Rajendra Nayak
2012-07-17 13:19       ` Rajendra Nayak
2012-07-17 13:34       ` Rajendra Nayak [this message]
2012-07-17 13:34         ` Rajendra Nayak
2012-07-17 13:46       ` Rob Herring
2012-07-17 13:46         ` Rob Herring
2012-07-17 13:54         ` Rajendra Nayak
2012-07-17 13:54           ` Rajendra Nayak
2012-07-17  0:43 ` Alexandre Pereira da Silva
2012-07-17  0:43   ` Alexandre Pereira da Silva
2012-07-17  4:58 ` Prashant Gaikwad
2012-07-17  4:58   ` Prashant Gaikwad

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=500569D5.3020508@ti.com \
    --to=rnayak@ti.com \
    --cc=aletes.xgr@gmail.com \
    --cc=archit@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@ti.com \
    --cc=pgaikwad@nvidia.com \
    --cc=robherring2@gmail.com \
    --cc=shawn.guo@linaro.org \
    --cc=tony@atomide.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.