From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <seanpaul@chromium.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the drm-msm-lumag tree
Date: Fri, 26 Apr 2024 12:22:37 +1000 [thread overview]
Message-ID: <20240426122237.4991a706@canb.auug.org.au> (raw)
In-Reply-To: <20240409120108.2303d0bd@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Hi all,
On Tue, 9 Apr 2024 12:01:08 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the drm-msm-lumag tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> lxml not found, skipping validation
>
> (lots of these)
>
> Introduced by commit
>
> 8f7abf0b86fe ("drm/msm: generate headers on the fly")
I am still seeing these wanrings. The above commit is now commit
0fddd045f88e ("drm/msm: generate headers on the fly")
in the drm-msm tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-04-26 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 2:01 linux-next: build warning after merge of the drm-msm-lumag tree Stephen Rothwell
2024-04-26 2:22 ` Stephen Rothwell [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=20240426122237.4991a706@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.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 read-only IMAP folder(s) and NNTP newsgroup(s).