public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: "Simon Glass" <sjg@chromium.org>,
	"Albert Aribaud" <albert.u.boot@aribaud.net>,
	"Tom Warren" <twarren@nvidia.com>,
	"Aaron Williams" <awilliams@marvell.com>,
	"Daniel Schwierzeck" <daniel.schwierzeck@gmail.com>,
	"York Sun" <yorksun@freescale.com>,
	"Priyanka Jain" <priyanka.jain@nxp.com>,
	"Oliver Graute" <oliver.graute@kococonnector.com>,
	"Meenakshi Aggarwal" <meenakshi.aggarwal@nxp.com>,
	"Wasim Khan" <wasim.khan@nxp.com>,
	"Joe Hershberger" <joe.hershberger@ni.com>,
	"Ramon Fried" <rfried.dev@gmail.com>,
	"Anatolij Gustschin" <agust@denx.de>,
	"Neil Armstrong" <narmstrong@baylibre.com>,
	"Jagan Teki" <jagan@amarulasolutions.com>,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Biwen Li" <biwen.li@nxp.com>,
	"Chaitanya Sakinam" <chaitanya.sakinam@nxp.com>,
	"Anji J" <anji.jagarlmudi@nxp.com>,
	"Michael Walle" <michael@walle.cc>,
	"Marek Behún" <marek.behun@nic.cz>,
	"Vladimir Oltean" <vladimir.oltean@nxp.com>,
	"Bin Meng" <bmeng.cn@gmail.com>,
	"Hou Zhiqiang" <Zhiqiang.Hou@nxp.com>,
	"Pali Rohár" <pali@kernel.org>,
	"Igal Liberman" <igall@marvell.com>,
	u-boot@lists.denx.de, u-boot-amlogic@groups.io
Subject: Re: [PATCH u-boot-dm v2] fdt_support: Add fdt_for_each_node_by_compatible() helper macro
Date: Tue, 18 Jan 2022 15:16:31 +0100	[thread overview]
Message-ID: <20220118151631.4e664bad@thinkpad> (raw)
In-Reply-To: <8f86f3c1-4c99-cb16-9ae2-e3c00ac1ebd9@denx.de>

On Tue, 18 Jan 2022 14:28:17 +0100
Stefan Roese <sr@denx.de> wrote:

> Hi Marek,
> 
> On 1/10/22 11:46, Marek Behún wrote:
> > From: Marek Behún <marek.behun@nic.cz>
> > 
> > Add macro fdt_for_each_node_by_compatible() to allow iterating over
> > fdt nodes by compatible string.
> > 
> > Convert various usages of
> >      off = fdt_node_offset_by_compatible(fdt, start, compat);
> >      while (off > 0) {
> >          code();
> >          off = fdt_node_offset_by_compatible(fdt, off, compat);
> >      }
> > and similar, to
> >      fdt_for_each_node_by_compatible(off, fdt, start, compat)
> >          code();
> > 
> > Signed-off-by: Marek Behún <marek.behun@nic.cz>
> > Reviewed-by: Stefan Roese <sr@denx.de>  
> 
> Apart from some merge issues, which I solved while appying, I'm seeing
> multiple problems with world building in CI / Azure. For example:
> 
> $ make turris_mox_defconfig
> $ make -s -j20
> drivers/phy/marvell/comphy_a3700.c: In function 
> 'find_available_node_by_compatible':
> drivers/phy/marvell/comphy_a3700.c:988:9: warning: implicit declaration 
> of function 'fdt_for_each_node_by_compatible'; did you mean 
> 'find_available_node_by_compatible'? [-Wimplicit-function-declaration]
>    988 |         fdt_for_each_node_by_compatible(offset, gd->fdt_blob, 
> offset,
>        |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>        |         find_available_node_by_compatible
> drivers/phy/marvell/comphy_a3700.c:989:52: error: expected ';' before 'if'
>    989 |                                         compatible)
>        |                                                    ^
>        |                                                    ;
>    990 |                 if (fdtdec_get_is_enabled(gd->fdt_blob, offset))
>        |                 ~~
> make[3]: *** [scripts/Makefile.build:254: 
> drivers/phy/marvell/comphy_a3700.o] Error 1
> make[2]: *** [scripts/Makefile.build:394: drivers/phy/marvell] Error 2
> make[1]: *** [scripts/Makefile.build:394: drivers/phy] Error 2
> make[1]: *** Waiting for unfinished jobs....
> make: *** [Makefile:1889: drivers] Error 2
> make: *** Waiting for unfinished jobs....
> 
> Could you please take a look and re-submit once this passes a world
> CI build? Or did I miss to apply some other patch before this one?

I sent v3 where I fixed compilation for various targets. Seems that
github's CI does not do all the tests anymore, and so didn't catch
them, otherwise I don't know how this could have happend.

There is one merge issue with Tom's master branch. I explained how to
resolve it in v3 after commit text.

Marek

      reply	other threads:[~2022-01-18 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 10:46 [PATCH u-boot-dm v2] fdt_support: Add fdt_for_each_node_by_compatible() helper macro Marek Behún
2022-01-12 20:04 ` Simon Glass
2022-01-12 22:24   ` Marek Behún
2022-01-13 13:41     ` Simon Glass
2022-01-18 13:28 ` Stefan Roese
2022-01-18 14:16   ` Marek Behún [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=20220118151631.4e664bad@thinkpad \
    --to=kabel@kernel.org \
    --cc=Zhiqiang.Hou@nxp.com \
    --cc=agust@denx.de \
    --cc=albert.u.boot@aribaud.net \
    --cc=andre.przywara@arm.com \
    --cc=anji.jagarlmudi@nxp.com \
    --cc=awilliams@marvell.com \
    --cc=biwen.li@nxp.com \
    --cc=bmeng.cn@gmail.com \
    --cc=chaitanya.sakinam@nxp.com \
    --cc=daniel.schwierzeck@gmail.com \
    --cc=igall@marvell.com \
    --cc=jagan@amarulasolutions.com \
    --cc=joe.hershberger@ni.com \
    --cc=marek.behun@nic.cz \
    --cc=meenakshi.aggarwal@nxp.com \
    --cc=michael@walle.cc \
    --cc=narmstrong@baylibre.com \
    --cc=oliver.graute@kococonnector.com \
    --cc=pali@kernel.org \
    --cc=priyanka.jain@nxp.com \
    --cc=rfried.dev@gmail.com \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --cc=twarren@nvidia.com \
    --cc=u-boot-amlogic@groups.io \
    --cc=u-boot@lists.denx.de \
    --cc=vladimir.oltean@nxp.com \
    --cc=wasim.khan@nxp.com \
    --cc=yorksun@freescale.com \
    /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