public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Eugeny S. Mints" <eugeny.mints@gmail.com>
Cc: pm list <linux-pm@lists.osdl.org>
Subject: Re: PowerOP, Whatchanged/Issues/TODO 2/2
Date: Sat, 2 Sep 2006 18:42:23 -0700	[thread overview]
Message-ID: <20060903014223.GB2481@kroah.com> (raw)
In-Reply-To: <44FA0FFF.9020807@gmail.com>

On Sun, Sep 03, 2006 at 03:13:03AM +0400, Eugeny S. Mints wrote:
> Greg,
> 
> Greg KH wrote:
> >On Sat, Sep 02, 2006 at 07:16:01PM +0400, Eugeny S. Mints wrote:
> >>whatchanged:
> >>- optional sysfs interface is added
> >>- code is moved under kernel/power
> >>- Greg's comments on kobject and coding style are addressed
> >>
> >>todo/issues:
> >>- better implementation for getting registered operating point names
> >>- move string parsing into powerop generic code
> >>- configfs for operating points creation from user space
> >
> >You forgot:
> >  - Handle module referencing counting issues.
> i'm discussing this and other issues you pointed out in a separate email.
> >
> >Also, no #ifdefs in the .c code please, that debugging stuff doesn't
> >have to look like that,
> do you mean CONFIG_POWEROP_SYSFS_OP_DEBUG_IF? Probably it's not a good name 
> but it's not a debugging code. it could be CONFIG_POWEROP_SYSFS_OP_HW_IF - 
> this special HW point might be useful in a production code.

No matter what the name, the #ifdef does not belong in the .c code in
the manner like this was done.  Please move it.

thanks,

greg k-h

  reply	other threads:[~2006-09-03  1:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-02 15:16 PowerOP, Whatchanged/Issues/TODO 2/2 Eugeny S. Mints
2006-09-02 18:33 ` Greg KH
2006-09-02 23:13   ` Eugeny S. Mints
2006-09-03  1:42     ` Greg KH [this message]
2006-09-03 12:44 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2006-09-14 14:38 Eugeny S. Mints
2006-09-29 21:44 Eugeny S. Mints

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=20060903014223.GB2481@kroah.com \
    --to=greg@kroah.com \
    --cc=eugeny.mints@gmail.com \
    --cc=linux-pm@lists.osdl.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