From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Intel Graphics" <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
"Christian König" <christian.koenig@amd.com>,
"Yunxiang Li" <Yunxiang.Li@amd.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the drm-misc-fixes tree
Date: Fri, 23 Jun 2023 09:09:59 +1000 [thread overview]
Message-ID: <20230623090959.7b5ce510@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
Hi all,
After merging the drm-misc-fixes tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/build_bug.h:5,
from include/linux/init.h:5,
from include/linux/io.h:10,
from include/linux/iosys-map.h:10,
from drivers/gpu/drm/ttm/ttm_resource.c:25:
drivers/gpu/drm/ttm/ttm_resource.c: In function 'ttm_lru_bulk_move_del':
drivers/gpu/drm/ttm/ttm_resource.c:117:40: error: suggest parentheses around '&&' within '||' [-Werror=parentheses]
117 | pos->first == res && pos->last == res)) {
| ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
include/linux/compiler.h:77:45: note: in definition of macro 'unlikely'
77 | # define unlikely(x) __builtin_expect(!!(x), 0)
| ^
cc1: all warnings being treated as errors
Caused by commit
4481913607e5 ("drm/ttm: fix bulk_move corruption when adding a entry")
I have used the drm-misc-fixes tree from next-20230622 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-06-22 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 23:09 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-26 21:32 linux-next: build failure after merge of the drm-misc-fixes tree Stephen Rothwell
2023-11-27 5:32 ` Ying Liu
2023-01-12 22:33 Stephen Rothwell
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=20230623090959.7b5ce510@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Yunxiang.Li@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).