From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] OMAP3: igep00x0: fix a build warning on IGEP boards
Date: Sat, 26 Jan 2013 08:42:38 -0500 [thread overview]
Message-ID: <5103DD4E.3080305@ti.com> (raw)
In-Reply-To: <1359202712-16731-1-git-send-email-javier.martinez@collabora.co.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/26/2013 07:18 AM, Javier Martinez Canillas wrote:
> commit b689cd5 OMAP3: use a single board file for IGEP devices
>
> introduced the following build warning:
>
> igep00x0.h:168:24: warning: backslash-newline at end of file
> [enabled by default]
>
> This patch fixes the issue.
>
> Signed-off-by: Javier Martinez Canillas
> <javier.martinez@collabora.co.uk>
Applied to u-boot-ti/master, thanks!
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRA91OAAoJENk4IS6UOR1WkK0QAIAiz5KHO1UQZVJXuTtsAulX
XtOAfmlEIKeFvGuAe1MWgXF7dnzODK+kfjZiZV8KW28xTp43EPi5V9i4yQtwGY67
GiYg+kL4VGBbLFCy2/taCe4S8oK1GC4kARxPjM/K371JqXvoXkpJcsRUllvmNvKy
a/CYNSWwRXc7Y2izHBHoc3/hVSiVYMVsqBZiklb5Sj/X+znxL+P8NE4Q6tS/erCa
W1wN7wAXNhZlGcZWyqL9fxjT1ex3sTfred8nsGh71UfWV8SYvMz8dkdVXFmhTFH3
E9HyYy4RrDnszdhGO0Wv6sKzRUKyXJQyqUkFOfRAKm+KzyPNzgThEtl034RTwgY6
8IwD5k/A1/o2WmDIVGPtodNUWaI23RzynhU9yafRWigCbN9VMUNJnBu4cftceomX
DQjwgAZy4UqCFrvL67HNgRTdBzozYFeeOj3WkZWIfVMMBAntaNIbffoSwPdtnyD7
BWDJuu/QCul1y6q3XQd1YvefdswykChW7Sfe9gXMS7c4PMcfBDexcubBzU4KQz8G
YpXf0nFkDdkeeZ37NfPSZl4d+ebFYvmyFL16S0KHcwY/gjA9iu1XEHbUOaPMv4Gs
18hc1uq72LbjELM+lHzbbt/92G9YqxyBTLAAiOCNUSYQ0LSoVB5fZXFsZOoK+tTN
PaXiZTi0OlS31TOxXvAV
=ZUp2
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-01-26 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 12:18 [U-Boot] [PATCH 1/1] OMAP3: igep00x0: fix a build warning on IGEP boards Javier Martinez Canillas
2013-01-26 13:42 ` Tom Rini [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=5103DD4E.3080305@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.