All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: arnd@arndb.de, cpufreq@lists.linux.org.uk,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	linuxppc-dev@ozlabs.org, paulus@samba.org, egor@pasemi.com
Subject: Re: [PATCH v3] [2.6.22] pasemi: cpufreq driver
Date: Sat, 28 Apr 2007 23:39:22 -0500	[thread overview]
Message-ID: <20070429043922.GA7478@lixom.net> (raw)
In-Reply-To: <20070429134059.feed0dc1.sfr@canb.auug.org.au>

On Sun, Apr 29, 2007 at 01:40:59PM +1000, Stephen Rothwell wrote:
> On Sat, 28 Apr 2007 22:50:21 -0400 Dominik Brodowski <linux@dominikbrodowski.net> wrote:
> >
> > Hi,
> > 
> > On Fri, Apr 27, 2007 at 12:46:01AM -0500, Olof Johansson wrote:
> > > +	max_freq = (u32*) get_property(cpu, "clock-frequency", NULL);
> > 
> > (u32) or (32*) ?
> 
> Neither, get_property now returns (void *) so casting is not needed or
> wanted.
> 
> Also, later in the patch, you modify the property value in place.  Do not do this. To help you remember, if you had not done the cast, gcc would have complained because get_property return a const void *.

Yep. It came along over from the cbe_cpufreq driver, which also does
it. I'll post a patch tomorrow or Monday unless someone else beats me
to it (the driver has already been merged).

> Also, get_property is now called of_get_property.

Sure, but keeping up with the API churn during other patch merging is a mess. It's easier to
make one final pass over all new code and fix it up once more later during the merge window.


-Olof

  reply	other threads:[~2007-04-29  4:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 20:46 [PATCH] [2.6.22] pasemi: cpufreq driver Olof Johansson
2007-04-25 23:47 ` Arnd Bergmann
2007-04-25 23:57   ` Olof Johansson
2007-04-26  1:57     ` Olof Johansson
2007-04-26  6:56   ` cbe_cpufreq crashes my machine Olof Johansson
2007-04-26  8:39     ` Benjamin Herrenschmidt
2007-04-26 23:07     ` [PATCH] cell: cbe_cpufreq cleanup and crash fix Olof Johansson
2007-04-27  5:22       ` [Cbe-oss-dev] " Akinobu Mita
2007-04-27  5:32         ` Olof Johansson
2007-04-27  5:33       ` [PATCH v2] " Olof Johansson
2007-04-27  7:55         ` Christian Krafft
2007-04-26  5:37 ` [PATCH v2] [2.6.22] pasemi: cpufreq driver Olof Johansson
2007-04-26  8:55   ` Arnd Bergmann
2007-04-26 16:48     ` Olof Johansson
2007-04-26 17:11       ` Arnd Bergmann
2007-04-26 19:05         ` Segher Boessenkool
2007-04-26 20:38           ` Olof Johansson
2007-04-27  0:10             ` Segher Boessenkool
2007-04-27  0:10               ` Segher Boessenkool
2007-04-26 20:26         ` Olof Johansson
2007-04-26 20:43           ` Arnd Bergmann
2007-04-26 10:26   ` Johannes Berg
2007-04-26 10:26     ` Johannes Berg
2007-04-26 20:37     ` Olof Johansson
2007-04-27  9:40       ` Johannes Berg
2007-04-27  9:40         ` Johannes Berg
2007-04-27 18:09         ` Olof Johansson
2007-04-27  5:46   ` [PATCH v3] " Olof Johansson
2007-04-29  2:50     ` Dominik Brodowski
2007-04-29  3:40       ` Stephen Rothwell
2007-04-29  4:39         ` Olof Johansson [this message]
2007-04-29  4:42       ` Olof Johansson

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=20070429043922.GA7478@lixom.net \
    --to=olof@lixom.net \
    --cc=arnd@arndb.de \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=egor@pasemi.com \
    --cc=linux@dominikbrodowski.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    /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.