From: Tom Rini <trini@konsulko.com>
To: christian.taedcke-oss@weidmueller.com
Cc: u-boot@lists.denx.de,
Christian Taedcke <christian.taedcke@weidmueller.com>,
Niel Fourie <lusus@denx.de>
Subject: Re: [PATCH v4 1/2] board/km/cent2: add include common.h
Date: Wed, 19 Jul 2023 16:28:11 -0400 [thread overview]
Message-ID: <20230719202811.GC1670569@bill-the-cat> (raw)
In-Reply-To: <20230719134544.235585-1-christian.taedcke-oss@weidmueller.com>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Wed, Jul 19, 2023 at 03:45:43PM +0200, christian.taedcke-oss@weidmueller.com wrote:
> From: Christian Taedcke <christian.taedcke@weidmueller.com>
>
> Including common.h before event.h is required, because the new fpga
> load event in event.h uses the size_t type.
>
> Signed-off-by: Christian Taedcke <christian.taedcke@weidmueller.com>
> ---
>
> Changes in v4:
> - add include common.h to kmcent2 board file
>
> board/keymile/kmcent2/kmcent2.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/board/keymile/kmcent2/kmcent2.c b/board/keymile/kmcent2/kmcent2.c
> index ed552c57b5..6dbaaa5457 100644
> --- a/board/keymile/kmcent2/kmcent2.c
> +++ b/board/keymile/kmcent2/kmcent2.c
> @@ -6,6 +6,7 @@
> * Copyright 2013 Freescale Semiconductor, Inc.
> */
>
> +#include <common.h>
> #include <event.h>
> #include <asm/cache.h>
> #include <asm/fsl_fdt.h>
No, we aren't adding common.h to more files. What in event.h needs some
other part of common.h that it's not getting today? common.h has
nothing more in it than other includes.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-07-19 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 13:45 [PATCH v4 1/2] board/km/cent2: add include common.h christian.taedcke-oss
2023-07-19 13:45 ` [PATCH v4 2/2] event: Add fpga load event christian.taedcke-oss
2023-07-19 20:30 ` Tom Rini
2023-07-19 19:11 ` [PATCH v4 1/2] board/km/cent2: add include common.h Simon Glass
2023-07-19 20:28 ` 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=20230719202811.GC1670569@bill-the-cat \
--to=trini@konsulko.com \
--cc=christian.taedcke-oss@weidmueller.com \
--cc=christian.taedcke@weidmueller.com \
--cc=lusus@denx.de \
--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