From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sunxi: Fix wrong pinmux names in arch/arm/cpu/armv7/sunxi/board.c
Date: Sun, 5 Jul 2015 14:24:56 +0200 [thread overview]
Message-ID: <55992218.7090204@redhat.com> (raw)
In-Reply-To: <1435611800-21833-1-git-send-email-merker@debian.org>
Hi Tom,
On 29-06-15 23:03, Karsten Merker wrote:
> Commit 487b3277d4f70bcb2e4a1930beb6438565f25910
> (sunxi: GPIO pin mux hardware-feature-specific function index defines)
> has removed and/or changed the names of various pinmux definitions,
> but has missed two instances in arch/arm/cpu/armv7/sunxi/board.c that
> still refer to the old-style names, which can now no longer be resolved.
> Use the new-style pinmux names instead.
>
> Signed-off-by: Karsten Merker <merker@debian.org>
Thanks for the patch, I already had the exact same patch from ChenYu
queued up, and even send a pull-req for it, but that bounced due to
conflicts. I've just send a new pull-req for v2015.07 with ChenYu's
fix in there, so this should be fixed for the next rc.
Regards,
Hans
prev parent reply other threads:[~2015-07-05 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 21:03 [U-Boot] [PATCH] sunxi: Fix wrong pinmux names in arch/arm/cpu/armv7/sunxi/board.c Karsten Merker
2015-07-05 12:24 ` Hans de Goede [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=55992218.7090204@redhat.com \
--to=hdegoede@redhat.com \
--cc=u-boot@lists.denx.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