From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl/nomadik : add MC1_a_2 pin MC1 function group list
Date: Mon, 10 Sep 2012 11:38:11 -0600 [thread overview]
Message-ID: <504E2583.4070602@wwwdotorg.org> (raw)
In-Reply-To: <1347265874-3342-1-git-send-email-linus.walleij@stericsson.com>
On 09/10/2012 02:31 AM, Linus Walleij wrote:
> From: Patrice Chotard <patrice.chotard@stericsson.com>
>
> Another possible pin configuration for the MC1 pin group.
I have no objection to this, but I wonder if these will keep trickling
in. Is it a good idea to audit the whole driver and add everything
that's missing in one go?
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stephen Warren <swarren@nvidia.com>,
Anmar Oueja <anmar.oueja@linaro.org>,
Patrice Chotard <patrice.chotard@stericsson.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] pinctrl/nomadik : add MC1_a_2 pin MC1 function group list
Date: Mon, 10 Sep 2012 11:38:11 -0600 [thread overview]
Message-ID: <504E2583.4070602@wwwdotorg.org> (raw)
In-Reply-To: <1347265874-3342-1-git-send-email-linus.walleij@stericsson.com>
On 09/10/2012 02:31 AM, Linus Walleij wrote:
> From: Patrice Chotard <patrice.chotard@stericsson.com>
>
> Another possible pin configuration for the MC1 pin group.
I have no objection to this, but I wonder if these will keep trickling
in. Is it a good idea to audit the whole driver and add everything
that's missing in one go?
next prev parent reply other threads:[~2012-09-10 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 8:31 [PATCH] pinctrl/nomadik : add MC1_a_2 pin MC1 function group list Linus Walleij
2012-09-10 8:31 ` Linus Walleij
2012-09-10 17:38 ` Stephen Warren [this message]
2012-09-10 17:38 ` Stephen Warren
2012-09-10 17:43 ` Linus Walleij
2012-09-10 17:43 ` 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=504E2583.4070602@wwwdotorg.org \
--to=swarren@wwwdotorg.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 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.