All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	robh+dt@kernel.org, nm@ti.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Len Brown <len.brown@intel.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] PM / OPP: Add missing doc comments
Date: Mon, 16 Nov 2015 13:14:52 +0100	[thread overview]
Message-ID: <20151116121452.GA22963@amd> (raw)
In-Reply-To: <d08ce7e01f31f9c8423b76f6bdf32dfbf93a6927.1447669859.git.viresh.kumar@linaro.org>

On Mon 2015-11-16 16:07:26, Viresh Kumar wrote:
> Few doc-style comments were missing, add them. Rearrange another one to
> match the sequence within the structure.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

Acked-by: Pavel Machek <pavel@ucw.cz>

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-11-16 12:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 10:37 [PATCH 0/3] PM / OPP: Parse opp-supported-hw/opp-<prop>-<name> bindings Viresh Kumar
2015-11-16 10:37 ` [PATCH 1/3] PM / OPP: Add missing doc comments Viresh Kumar
2015-11-16 10:37   ` Viresh Kumar
2015-11-16 12:14   ` Pavel Machek [this message]
2015-11-18 22:29   ` Stephen Boyd
2015-11-16 10:37 ` [PATCH 2/3] PM / OPP: Parse 'opp-supported-hw' binding Viresh Kumar
2015-11-16 10:37   ` Viresh Kumar
2015-11-18 22:53   ` Stephen Boyd
2015-11-19  2:00     ` Viresh Kumar
2015-11-19  3:02       ` Viresh Kumar
2015-11-16 10:37 ` [PATCH 3/3] PM / OPP: Parse 'opp-<prop>-<name>' bindings Viresh Kumar
2015-11-16 10:37   ` Viresh Kumar
2015-11-19  1:12   ` Stephen Boyd
2015-11-19  3:00     ` Viresh Kumar

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=20151116121452.GA22963@amd \
    --to=pavel@ucw.cz \
    --cc=gregkh@linuxfoundation.org \
    --cc=len.brown@intel.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=viresh.kumar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.