public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
	Stephen Warren <swarren@nvidia.com>,
	Kevin Hilman <khilman@linaro.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Hebbar Gururaja <gururaja.hebbar@ti.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Wolfram Sang <wsa@the-dreams.de>, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] drivers: pinctrl: add active state to core
Date: Wed, 12 Jun 2013 11:35:09 -0700	[thread overview]
Message-ID: <20130612183509.GV8164@atomide.com> (raw)
In-Reply-To: <20130611160322.GB20352@kroah.com>

* Greg Kroah-Hartman <gregkh@linuxfoundation.org> [130611 09:08]:
> On Tue, Jun 11, 2013 at 10:16:56AM +0200, Linus Walleij wrote:
> > From: Linus Walleij <linus.walleij@linaro.org>
> > 
> > In addition to the recently introduced pinctrl core
> > control, the PM runtime pin control for the OMAP platforms
> > require a fourth state in addtition to the default, idle and
> > sleep states already handled by the core: an explicit "active"
> > state. Let's introduce this to the core in addition to the
> > other states already defined.
> > 
> > Cc: Hebbar Gururaja <gururaja.hebbar@ti.com>
> > Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > Cc: Stephen Warren <swarren@wwwdotorg.org>
> > Cc: Wolfram Sang <wsa@the-dreams.de>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: Mark Brown <broonie@kernel.org>
> > Cc: Kevin Hilman <khilman@linaro.org>
> > Suggested-by: Tony Lindgren <tony@atomide.com>
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > ---
> > Greg: need your ACK on this to merge it through the pinctrl
> > tree.
> > ---
> >  drivers/base/pinctrl.c                |  8 +++++++-
> >  drivers/pinctrl/core.c                | 15 +++++++++++++++
> 
> For anything that just touches drivers/base/pinctrl.c, you don't need my
> ack, that's your code, you can do whatever you want with it :)
> 
> But here you go anyway:
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Acked-by: Tony Lindgren <tony@atomide.com>

  reply	other threads:[~2013-06-12 18:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11  8:16 [PATCH] drivers: pinctrl: add active state to core Linus Walleij
2013-06-11 16:03 ` Greg Kroah-Hartman
2013-06-12 18:35   ` Tony Lindgren [this message]
2013-06-11 16:33 ` Stephen Warren
2013-06-11 19:53   ` Linus Walleij
2013-06-12 18:33     ` Tony Lindgren
2013-06-13 19:31       ` Stephen Warren
2013-06-14  8:46         ` Tony Lindgren
2013-06-14 15:23           ` Stephen Warren
2013-06-17  7:29             ` Tony Lindgren
2013-06-13 19:38     ` Stephen Warren
2013-06-16 10:01 ` Linus Walleij

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=20130612183509.GV8164@atomide.com \
    --to=tony@atomide.com \
    --cc=broonie@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gururaja.hebbar@ti.com \
    --cc=khilman@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.org \
    --cc=wsa@the-dreams.de \
    /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