All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	DTML <devicetree@vger.kernel.org>,
	Frank Rowand <frowand.list@gmail.com>
Subject: Re: [GIT PULL] Devicetree updates for v5.16
Date: Mon, 8 Nov 2021 08:57:27 -0600	[thread overview]
Message-ID: <CAL_Jsq+HDXdJL69ybGBM16Nm4giS62ZP+5k3_OGsharrRj-PiQ@mail.gmail.com> (raw)
In-Reply-To: <CAFr9PXnftX3k3C0sAt=qF4fgOS1apF_j4REqJXKk=wzCTVnBfw@mail.gmail.com>

On Mon, Nov 8, 2021 at 7:13 AM Daniel Palmer <daniel@0x0f.com> wrote:
>
> Hi Rob,
>
> On Wed, 3 Nov 2021 at 06:57, Rob Herring <robh@kernel.org> wrote:
> > Rob Herring (22):
> >       kbuild: Enable DT schema checks for %.dtb targets
>
> Sorry for replying to a pull request. I couldn't find the original
> patch email for this commit to reply.

FYI, the link is in the commit and 'b4' makes it easy to get the mbox
to reply to. It's quite nice to be able to reply to *anything*.

> Anyhow, the above commit makes buildroot unhappy.
> I see this when trying to build any of my buildroot environments:
> scripts/dtc/Makefile:23: *** dtc needs libyaml for DT schema
> validation support. Install the necessary libyaml development
> package..  Stop.

If you fix this, then the next thing you will get is the dtschema
python package is needed.

> I think this is some mess with pkg-config from somewhere (the host
> distro, the buildroot host side,..) saying libyaml is available but
> when the build actually happens the header it wants isn't actually
> where it thinks. I think this is a pre-existing problem with
> buildroot.
> buildroot takes a list of the dtbs that you want to build and keep in
> it's config and calls make with that list in the kernel build. So this
> commit causes this issue to trigger when buildroot tries to build the
> configured dtbs.
>
> Not sure what the fix is and I think it's probably a buildroot problem.

I suppose we can keep schema checks optional here, but my intention in
this patch was moving towards the checks being required rather than a
separate target. So we'd be kicking the problem down the road.

Rob

      reply	other threads:[~2021-11-08 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 21:56 [GIT PULL] Devicetree updates for v5.16 Rob Herring
2021-11-03  5:38 ` pr-tracker-bot
2021-11-08 13:15 ` Daniel Palmer
2021-11-08 14:57   ` Rob Herring [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=CAL_Jsq+HDXdJL69ybGBM16Nm4giS62ZP+5k3_OGsharrRj-PiQ@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=daniel@0x0f.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.