From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] OMAP5: I2C: Enable i2c5 clocks
Date: Mon, 8 Apr 2013 08:34:40 -0400 [thread overview]
Message-ID: <5162B960.9090900@ti.com> (raw)
In-Reply-To: <51628F66.7010406@mm-sol.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/08/2013 05:35 AM, Lubomir Popov wrote:
> One more thing I would like to clarify to myself: in your patch
> series of Apr. 1 you rename the omap5_evm to omap5_uevm. On the
> other hand, uEVM was the TI-internal name for the PandaBoard5, and
> the evm was known as sEVM. Doesn't this cause confusion? After all,
> these are two quite different hardware platforms.
Moving forward, there is only uEVM and sEVM doesn't exist.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRYrlgAAoJENk4IS6UOR1WkBoP/iIMkPldiFmQRmDRCiuvoprd
0qq7Cak8Y1XF1YYwGARXW4Hup/Tvz6UpPxJx5oa5ESTIm0Km3CcBHw+0j3OuLYm5
K3XnXQ0Y+WHBf0V5uZJMMN7PqeoIV/R1SaKKp3421jPuaP9suBiihfKGP5Z78jl7
gXM14711xk4UgGitZc4ER73G6mlwOQyFABGONxyoAOhDuVN2BuPcx69OYUINKDrw
h9iW6JTtVwe+5JVIMPDYqUZJALgbeKsjMBOHjsFMahHlVGHDJ+SAKZ4IWnfKi8tY
J5Wi6PeeSqqokhL+dcMRWDRq5A7ufU9beRkFdmuWJRkFNhc7Jpqd/8kxctGbgf3t
NkI7UrbCTilTJnvv9/oEu+MVx6bBOXfD2uOy5m6kaOqZG+XFN1KsGJGs/PsevklL
zmwxYfDNSJl0DReMK8Wc7zFKN+vbpRDkcFGkG3yJAfTkWWm+fNfhygM/+aFNvT1K
NQivqSf546MbOU4CWWkhaF6pSivObT7br9yHP17QLLJnR2uWINzKu9kk2fcRRltJ
Q+jdQ6XLUDJ/7H22GhtrWNvzLCqphi/v7dpEtfF/0/syUnUnOEYOCtvUulRaMyKT
bHdaylb1lOJtwaf0iGROR6Jb9DuRUBLoRP+iM7PjPQpqhxrONIs6RWe76/0l5Gaf
nnLD8mOPhKBItASlevtK
=lm6d
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-08 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 15:52 [U-Boot] [PATCH v2] OMAP5: I2C: Enable i2c5 clocks Lubomir Popov
2013-04-08 6:09 ` Sricharan R
2013-04-08 9:35 ` Lubomir Popov
2013-04-08 12:34 ` Tom Rini [this message]
2013-04-09 6:31 ` Sricharan R
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=5162B960.9090900@ti.com \
--to=trini@ti.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 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.