From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3: Update Overo pin mux for new expansion board
Date: Mon, 30 Mar 2009 17:05:04 +0200 [thread overview]
Message-ID: <20090330150504.GD21302@game.jcrosoft.org> (raw)
In-Reply-To: <49D0C930.5030400@googlemail.com>
On 15:29 Mon 30 Mar , Dirk Behme wrote:
> Jean-Christophe PLAGNIOL-VILLARD wrote:
>> On 20:00 Mon 16 Mar , Dirk Behme wrote:
>>> A new Overo expansion board uses GPIO 14, 21, 22 and 23 for LED's and
>>> switches. This patch changes the pinmux configuration for those pins.
>>> They were previously set up for unused MMC3_DAT4-7.
>>>
>>> Signed-off-by: Steve Sakoman <steve@sakoman.com>
>>> ---
>>>
>>> Patch is against recent mainline commit
>>> 'b3dd629e78870ba2dc9f8032978721c0fa02a856'
>>> "Prepare 2009.03-rc2"
>> sorry NACK
>>
>> Please send it correctly because git am will take the information from the
>> email Hearder and I do not want to fix it manually
>
> Hmm, I sent this patch the same way I did with the other patches. And I
> can't see anything obviously wrong. Please give some details what you
> think might be wrong with this patch (header?).
Based on the patch info your not the Author of the patch so it must be the
same in the Mail Header info
Best Regards,
J.
next prev parent reply other threads:[~2009-03-30 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 19:00 [U-Boot] [PATCH] OMAP3: Update Overo pin mux for new expansion board Dirk Behme
2009-03-29 18:42 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-30 13:29 ` Dirk Behme
2009-03-30 15:05 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-03-30 17:44 ` Wolfgang Denk
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=20090330150504.GD21302@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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