netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Federico Vaga <federico.vaga@gmail.com>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
	Giancarlo Asnaghi <giancarlo.asnaghi@st.com>,
	Alan Cox <alan@linux.intel.com>,
	Alessandro Rubini <rubini@gnudd.com>,
	linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] c_can_pci: generic module for c_can on PCI
Date: Tue, 12 Jun 2012 16:46:32 +0200	[thread overview]
Message-ID: <4FD75648.7060702@pengutronix.de> (raw)
In-Reply-To: <2105333.GQGP4hKIYU@harkonnen>

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

On 06/12/2012 04:25 PM, Federico Vaga wrote:
>>> +out_free_clock:
>>> +	if (!priv->priv)
>>
>>            ^^^
>>
>> looks fishy
> 
> Also c_can_platform.c use priv->priv when it needs to get clk. I can add 
> a comment to specify what the statement do.

> +out_free_clock:
> +	if (!priv->priv)
> +		clk_put(priv->priv);

Why do you call clk_put on priv->priv, if priv->priv is NULL?

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-06-12 14:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 20:59 [PATCH] STA2X11 CAN: CAN driver for the STA2X11 board Federico Vaga
2012-05-18  6:00 ` Wolfgang Grandegger
2012-05-26  8:36   ` Federico Vaga
2012-05-26 19:57     ` Wolfgang Grandegger
2012-06-04 13:32       ` generic module for c-can on pci Federico Vaga
2012-06-04 13:32         ` [PATCH RFC] c_can_pci: generic module for c_can on PCI Federico Vaga
2012-06-04 14:04           ` Marc Kleine-Budde
2012-06-12 14:25             ` Federico Vaga
2012-06-12 14:46               ` Marc Kleine-Budde [this message]
2012-06-12 14:53                 ` Federico Vaga
2012-06-04 15:56           ` Alan Cox
2012-06-04 16:45             ` Federico Vaga
2012-06-05  3:42               ` Bhupesh SHARMA
2012-06-05 11:19                 ` Federico Vaga
2012-06-05 13:04                   ` Bhupesh SHARMA
2012-06-05 13:13                   ` Alessandro Rubini
2012-06-05 13:21                     ` Marc Kleine-Budde
2012-06-05 13:22                     ` Bhupesh SHARMA
2012-06-05 13:30                     ` Alessandro Rubini
2012-06-05 15:12                       ` AnilKumar, Chimata
2012-06-05 16:50                       ` Alessandro Rubini
2012-06-06  3:50                         ` Bhupesh SHARMA
2012-06-11 13:18                           ` Federico Vaga
2012-06-11 14:21                             ` Wolfgang Grandegger
2012-06-04 16:45           ` Alessandro Rubini
2012-06-11 13:51             ` Wolfgang Grandegger
2012-06-11 14:23             ` Alessandro Rubini
2012-06-11 14:09           ` Wolfgang Grandegger

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=4FD75648.7060702@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=alan@linux.intel.com \
    --cc=federico.vaga@gmail.com \
    --cc=giancarlo.asnaghi@st.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rubini@gnudd.com \
    --cc=wg@grandegger.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).