From: Kevin Hilman <khilman@deeprootsystems.com>
To: Chaithrika U S <chaithrika@ti.com>
Cc: netdev@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
davem@davemloft.net
Subject: Re: [PATCH] TI DaVinci EMAC: Convert to dev_pm_ops
Date: Fri, 12 Mar 2010 15:28:47 -0800 [thread overview]
Message-ID: <87zl2d3ys0.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1268296676-12514-1-git-send-email-chaithrika@ti.com> (Chaithrika U. S.'s message of "Thu\, 11 Mar 2010 14\:07\:56 +0530")
Chaithrika U S <chaithrika@ti.com> writes:
> Migrate from the legacy PM hooks to use dev_pm_ops structure.
>
> Signed-off-by: Chaithrika U S <chaithrika@ti.com>
Acked-by: Kevin Hilman <khilman@deeprootsystems.com>
next prev parent reply other threads:[~2010-03-12 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 8:37 [PATCH] TI DaVinci EMAC: Convert to dev_pm_ops Chaithrika U S
2010-03-12 23:28 ` Kevin Hilman [this message]
2010-03-15 22:48 ` David Miller
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=87zl2d3ys0.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=chaithrika@ti.com \
--cc=davem@davemloft.net \
--cc=davinci-linux-open-source@linux.davincidsp.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).