From: Nishanth Menon <nm@ti.com>
To: linux-pm@vger.kernel.org
Cc: Nishanth Menon <nm@ti.com>,
Rajagopal Venkat <rajagopal.venkat@linaro.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: [for-next PATCH 0/2] PM / devfreq: more documentation fixes
Date: Thu, 25 Oct 2012 18:10:12 -0500 [thread overview]
Message-ID: <1351206614-23993-1-git-send-email-nm@ti.com> (raw)
The following patches apply on top of
Rafael's pm-devfreq-next branch on
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
and introduced due to warnings of accepted patches.
I dont seem to have the original emails in my mailbox anymore
So apologies of not replying inline to the original patches.
I have tried to provide link to the relevant patchworks link
of the original patch if I could find them.
I hope we will keep the documentation clean ahead :)
Nishanth Menon (2):
PM / devfreq: more documentation warning fixes
PM / devfreq: more documentation warning fixes next set
drivers/devfreq/devfreq.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Cc: Rajagopal Venkat <rajagopal.venkat@linaro.org>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Cc: Kyungmin Park <kyungmin.park@samsung.com>
Regards,
Nishanth Menon
--
1.7.9.5
next reply other threads:[~2012-10-25 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 23:10 Nishanth Menon [this message]
2012-10-25 23:10 ` [for-next PATCH 1/2] PM / devfreq: more documentation warning fixes Nishanth Menon
2012-10-26 0:05 ` Rafael J. Wysocki
2012-10-25 23:10 ` [for-next PATCH 2/2] PM / devfreq: more documentation warning fixes next set Nishanth Menon
2012-10-26 0:05 ` Rafael J. Wysocki
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=1351206614-23993-1-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rajagopal.venkat@linaro.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