From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux-Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
dri-devel <dri-devel@lists•freedesktop.org>
Subject: Re: linux-next: Tree for Feb 19 (gpu/drm/pl111/)
Date: Mon, 19 Feb 2018 10:30:06 -0800 [thread overview]
Message-ID: <b1028c02-9633-47bf-e930-a20926e14ca9@infradead.org> (raw)
In-Reply-To: <5a671632-f746-52d2-1a9c-1e72a7e2f42b@infradead.org>
[add Eric + dri-devel]
On 02/19/18 09:26, Randy Dunlap wrote:
> On 02/18/18 18:14, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20180216:
>>
>> The nand tree gained a conflict against Linus' tree.
>>
>> The drm tree gained conflicts against Linus' tree.
>
> on i386 (randconfig):
>
> warning: (DRM_PL111) selects DRM_DUMB_VGA_DAC which has unmet direct dependencies (HAS_IOMEM && DRM && DRM_BRIDGE && OF)
>
> and then
>
> ../drivers/gpu/drm/bridge/dumb-vga-dac.c: In function 'dumb_vga_probe':
> ../drivers/gpu/drm/bridge/dumb-vga-dac.c:207:13: error: 'struct drm_bridge' has no member named 'of_node'
> vga->bridge.of_node = pdev->dev.of_node;
> ^
>
>
--
~Randy
_______________________________________________
dri-devel mailing list
dri-devel@lists•freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next parent reply other threads:[~2018-02-19 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180219131426.14ecac87@canb.auug.org.au>
[not found] ` <5a671632-f746-52d2-1a9c-1e72a7e2f42b@infradead.org>
2018-02-19 18:30 ` Randy Dunlap [this message]
2018-02-20 10:07 ` linux-next: Tree for Feb 19 (gpu/drm/pl111/) Thierry Reding
2018-02-20 10:29 ` [PATCH] drm/pl111: Remove reverse dependency on DRM_DUMB_VGA_DAC Thierry Reding
2018-02-20 11:14 ` Archit Taneja
2018-02-26 10:16 ` Archit Taneja
2018-02-21 7:05 ` Linus Walleij
2018-02-22 20:10 ` Eric Anholt
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=b1028c02-9633-47bf-e930-a20926e14ca9@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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