xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien@xen.org>
To: Vikram Garhwal <fnu.vikram@xilinx.com>, xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, bertrand.marquis@arm.com,
	volodymyr_babchuk@epam.com
Subject: Re: [XEN][PATCH v3 1/1] Update libfdt to v1.6.1
Date: Mon, 8 Nov 2021 10:37:31 +0000	[thread overview]
Message-ID: <caac2d2b-46a7-e12b-7cb0-ac1b7791d8a1@xen.org> (raw)
In-Reply-To: <1636147719-80482-2-git-send-email-fnu.vikram@xilinx.com>

Hi Vikram,

On 05/11/2021 21:28, Vikram Garhwal wrote:
> Update libfdt to v1.6.1 of libfdt taken from git://github.com/dgibson/dtc.
> This update is done to support device tree overlays.
> 
> A few minor changes are done to make it compatible with Xen:
>      fdt_overlay.c: overlay_fixup_phandle()
> 
>          Replace strtoul() with simple_strtoul() as strtoul() is not available in
>          Xen lib and included lib.h.
> 
>          Change char *endptr to const char *endptr.

I would clarify this is a requirement to use simple_strtoul().

[...]

> diff --git a/xen/include/xen/libfdt/libfdt_env.h b/xen/include/xen/libfdt/libfdt_env.h
> index 035bf75..03380d5 100644
> --- a/xen/include/xen/libfdt/libfdt_env.h
> +++ b/xen/include/xen/libfdt/libfdt_env.h
> @@ -1,22 +1,98 @@
> -#ifndef _LIBFDT_ENV_H
> -#define _LIBFDT_ENV_H
> +/* SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause) */
> +#ifndef LIBFDT_ENV_H
> +#define LIBFDT_ENV_H
> +/*
> + * libfdt - Flat Device Tree manipulation
> + * Copyright (C) 2006 David Gibson, IBM Corporation.
> + * Copyright 2012 Kim Phillips, Freescale Semiconductor.
> + */
>   
> +#include <xen/config.h>

The build system should always include <xen/config.h> automagically. So 
can you clarify why this is necessary?

>   #include <xen/types.h>
>   #include <xen/string.h>
>   #include <asm/byteorder.h>
> +#include <xen/stdbool.h>

We usually order the headers so <xen/...> are first and then <asm/...>. 
They are then ordered alphabetically within themself.

But it is not clear why you are adding <xen/stdbool.h> as AFAICT it is 
already going to be included by existing headers. Did you see an error 
without including it?

Cheers,

-- 
Julien Grall


  reply	other threads:[~2021-11-08 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 21:28 [XEN][PATCH v3 0/1] Update libfdt to v1.6.1 Vikram Garhwal
2021-11-05 21:28 ` [XEN][PATCH v3 1/1] " Vikram Garhwal
2021-11-08 10:37   ` Julien Grall [this message]
2021-11-09  7:47     ` Vikram Garhwal

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=caac2d2b-46a7-e12b-7cb0-ac1b7791d8a1@xen.org \
    --to=julien@xen.org \
    --cc=bertrand.marquis@arm.com \
    --cc=fnu.vikram@xilinx.com \
    --cc=sstabellini@kernel.org \
    --cc=volodymyr_babchuk@epam.com \
    --cc=xen-devel@lists.xenproject.org \
    /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;
as well as URLs for NNTP newsgroup(s).