From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 54/81] ARM: shmobile: sh73a0: Use driver-provided pinmux info
Date: Tue, 18 Dec 2012 02:18:31 +0000 [thread overview]
Message-ID: <20121218021831.GO28065@verge.net.au> (raw)
In-Reply-To: <1355611915-25060-55-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Sat, Dec 15, 2012 at 11:51:28PM +0100, Laurent Pinchart wrote:
> Pinmux info for the sh73a0 is now provided by pinmux drivers. Remove the
> duplicate copy in arch code.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
> arch/arm/mach-shmobile/Makefile | 5 -
> arch/arm/mach-shmobile/pfc-sh73a0.c | 2829 ---------------------------------
> arch/arm/mach-shmobile/setup-sh73a0.c | 25 +
> 3 files changed, 25 insertions(+), 2834 deletions(-)
> delete mode 100644 arch/arm/mach-shmobile/pfc-sh73a0.c
Acked-by: Simon Horman <horms+renesas@verge.net.au>
prev parent reply other threads:[~2012-12-18 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 22:51 [PATCH v3 54/81] ARM: shmobile: sh73a0: Use driver-provided pinmux info Laurent Pinchart
2012-12-18 2:18 ` Simon Horman [this message]
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=20121218021831.GO28065@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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).