From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 2/3] include/linux/fb.h: Add a missing include for 'list.h'
Date: Mon, 7 Oct 2013 16:04:56 -0400 [thread overview]
Message-ID: <20131007200456.GZ15917@bill-the-cat> (raw)
In-Reply-To: <1380798280-3449-3-git-send-email-otavio@ossystems.com.br>
On Thu, Oct 03, 2013 at 08:04:39AM -0300, Otavio Salvador wrote:
> The modelist data uses the list definition but the 'list.h' header
> were not being included. The build failure is bellow:
>
> ,----
> | In file included from yyyy.c:16:0:
> | .../u-boot/include/linux/fb.h:503:19: error: field 'modelist' has incomplete type
> | struct list_head modelist; /* mode list */
> | ^
> | make[1]: *** [yyyy.o] Error 1
> | make[1]: Leaving directory `.../u-boot/board/xxx/yyyy'
> | make: *** [board/xxx/yyyy/libyyyy.o] Error 2
> `----
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131007/d79af6bb/attachment.pgp>
next prev parent reply other threads:[~2013-10-07 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 11:04 [U-Boot] [PATCH v3 0/3] Trivial patches ready for merging Otavio Salvador
2013-10-03 11:04 ` [U-Boot] [PATCH v3 1/3] mtd: Fix function description in part_validate comment Otavio Salvador
2013-10-07 20:04 ` [U-Boot] [U-Boot, v3, " Tom Rini
2013-10-03 11:04 ` [U-Boot] [PATCH v3 2/3] include/linux/fb.h: Add a missing include for 'list.h' Otavio Salvador
2013-10-07 20:04 ` Tom Rini [this message]
2013-10-03 11:04 ` [U-Boot] [PATCH v3 3/3] doc: Fix a typo in the description in doc/README.JFFS2_NAND Otavio Salvador
2013-10-07 20:05 ` [U-Boot] [U-Boot, v3, " Tom Rini
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=20131007200456.GZ15917@bill-the-cat \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox