From: Jeff Garzik <jeff@garzik.org>
To: Ayaz Abdulla <aabdulla@nvidia.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
Andrew Morton <akpm@osdl.org>, nedev <netdev@vger.kernel.org>
Subject: Re: [PATCH 2/4] forcedeth: fix power management support
Date: Thu, 24 May 2007 18:00:11 -0400 [thread overview]
Message-ID: <46560AEB.8040402@garzik.org> (raw)
In-Reply-To: <465237E8.1060005@nvidia.com>
Ayaz Abdulla wrote:
> This patch fixes the power management functions. It includes lowering
> the phy speed to conserve power.
>
> Signed-off-by: Ayaz Abdulla <aabdulla@nvidia.com>
Several issues here:
1) Your patch description needs to explain the problems in the power
management code. It is self-evident from the patch what functions are
being changed, and that you feel these changes constitute a fix. But
beyond that... no information is given.
2) Lowering the phy speed to conserve power is not an appropriate change
for a "bug fix only" 2.6.22-rc cycle AFAICS. Unless there is a
compelling argument otherwise, I feel this change should be in a
separate patch, submitted for 2.6.23 (netdev-2.6.git#upstream).
3) You left in debugging printk's, which is sloppy:
+ dprintk(KERN_DEBUG "forcedeth: nv_suspend\n");
4) You save PCI config space twice:
pci_save_state(pdev);
+
+ /* save any device state */
+ np->saved_phyinterface = readl(base + NvRegPhyInterface);
+ for (i = 0; i < 64; i++) {
+ pci_read_config_dword(pdev, i*4, &np->saved_config_space[i]);
So, this needs work.
next prev parent reply other threads:[~2007-05-24 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 0:23 [PATCH 2/4] forcedeth: fix power management support Ayaz Abdulla
2007-05-24 22:00 ` Jeff Garzik [this message]
2007-05-29 9:31 ` Andi Kleen
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=46560AEB.8040402@garzik.org \
--to=jeff@garzik.org \
--cc=aabdulla@nvidia.com \
--cc=akpm@osdl.org \
--cc=manfred@colorfullife.com \
--cc=netdev@vger.kernel.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).