From: Thierry Reding <thierry.reding@gmail.com>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: Simona Vetter <simona.vetter@ffwll.ch>,
DRI <dri-devel@lists.freedesktop.org>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Dharma Balasubiramani <dharma.b@microchip.com>,
Maxime Ripard <mripard@kernel.org>,
Manikandan Muralidharan <manikandan.m@microchip.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the pinctrl-intel tree
Date: Thu, 7 May 2026 14:15:36 +0200 [thread overview]
Message-ID: <afyCC_FE9QL5VBBm@orome> (raw)
In-Reply-To: <3b729608ad4bc3bb161c3779a9768b12@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
On Thu, May 07, 2026 at 12:47:48PM +0200, Thierry Reding wrote:
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
Sorry about the misleading subject. This was indeed introduced after
merging the drm-misc tree, not pinctrl-intel. I need to look closer at
the templates that are generated.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-07 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 10:47 linux-next: build failure after merge of the pinctrl-intel tree Thierry Reding
2026-05-07 12:15 ` Thierry Reding [this message]
2026-05-11 6:09 ` Manikandan.M
-- strict thread matches above, loose matches on Subject: below --
2022-10-18 2:13 Stephen Rothwell
2022-10-18 2:20 ` Stephen Rothwell
2022-10-18 12:29 ` Andy Shevchenko
2020-08-20 1:30 Stephen Rothwell
2020-08-20 9:40 ` Andy Shevchenko
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=afyCC_FE9QL5VBBm@orome \
--to=thierry.reding@gmail.com \
--cc=dharma.b@microchip.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=manikandan.m@microchip.com \
--cc=mripard@kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=thierry.reding@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 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.