linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH] powersave_nap cleanup
Date: Fri, 9 Jun 2006 12:33:26 -0500	[thread overview]
Message-ID: <20060609173326.GA8934@localdomain> (raw)
In-Reply-To: <17545.15326.767523.342562@cargo.ozlabs.ibm.com>

Paul Mackerras wrote:
> Nathan Lynch writes:
> 
> > Rename machdep_calls.power_save to machdep_calls.powersave_nap to make
> > more apparent the connection with the powersave_nap sysctl.
> 
> Hmmm, it's possibly a bit confusing to have a variable and a function
> with the same name...

Heh, I thought you had suggested doing that, maybe I misunderstood.

So, what to do?  Leave the machdep_calls.power_save name as it is?

      reply	other threads:[~2006-06-09 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26 14:02 [RFC/PATCH] powersave_nap cleanup Nathan Lynch
2006-06-09  9:14 ` Paul Mackerras
2006-06-09 17:33   ` Nathan Lynch [this message]

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=20060609173326.GA8934@localdomain \
    --to=ntl@pobox.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 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).