From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: build warning after merge of the drm tree
Date: Thu, 4 May 2017 11:42:30 +1000 [thread overview]
Message-ID: <20170504114230.02793761@canb.auug.org.au> (raw)
In-Reply-To: <tencent_62AF37B85899E2EA593CCE3B@qq.com>
Hi Jeffy,
On Thu, 4 May 2017 09:18:12 +0800 "Jeffy" <jeffy.chen@rock-chips.com> wrote:
>
> it should be fixed by "Arnd Bergmann"<arnd@arndb.de>(thanks a lot by the way) in:
>
> 4a85aae multi_v7_defconfig: make Rockchip DRM drivers built-in
Thanks for the heads up, I will await the arm-soc merges.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-05-04 1:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 22:33 linux-next: build warning after merge of the drm tree Stephen Rothwell
[not found] ` <tencent_62AF37B85899E2EA593CCE3B@qq.com>
2017-05-04 1:42 ` 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=20170504114230.02793761@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-arm-kernel@lists.infradead.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