linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: Add one-register-per-pin type device tree based pinctrl driver
Date: Thu, 21 Jun 2012 10:09:03 +0200	[thread overview]
Message-ID: <CACRpkdbi1V+Y6cMSNX_Rk_ccjk35eB6c_EJbNY620QFS8F_KRQ@mail.gmail.com> (raw)
In-Reply-To: <20120619135600.GX12766@atomide.com>

On Tue, Jun 19, 2012 at 3:56 PM, Tony Lindgren <tony@atomide.com> wrote:

> Below is the pinctrl-single patch updated with hopefully all the Stephen's
> comments addressed. The binding still needs to be looked at, see relevant
> parts of the discussion below.

I am happy with the code and the way it interacts with the pinctrl subsystem!

Now all I need to merge this is a few ACKs from select people, and
since this has a deep impact on the way device tree is used I would
*really* like for Grant or Rob to ACK it.

Yours,
Linus Walleij

  reply	other threads:[~2012-06-21  8:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 13:58 [PATCH] pinctrl: Add one-register-per-pin type device tree based pinctrl driver Tony Lindgren
2012-06-14 23:12 ` Stephen Warren
2012-06-15  9:49   ` Tony Lindgren
2012-06-15 16:17     ` Stephen Warren
2012-06-18  5:50       ` Tony Lindgren
2012-06-19 13:56         ` Tony Lindgren
2012-06-21  8:09           ` Linus Walleij [this message]
2012-06-21 22:13           ` Stephen Warren
2012-06-22  8:39             ` Tony Lindgren
2012-06-22 17:32               ` Stephen Warren
2012-06-26 13:43                 ` Tony Lindgren
2012-06-26 17:05                   ` Stephen Warren
2012-06-27 10:28                     ` Tony Lindgren
2012-07-10  9:11                       ` Tony Lindgren
2012-07-14 20:16                         ` Linus Walleij
2012-07-16  7:10                           ` Tony Lindgren

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=CACRpkdbi1V+Y6cMSNX_Rk_ccjk35eB6c_EJbNY620QFS8F_KRQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).