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>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: linux-next: Tree for Nov 19 (i915)
Date: Tue, 19 Nov 2019 07:33:45 -0800 [thread overview]
Message-ID: <1d30acd4-9947-d228-967f-c4e76ebca832@infradead.org> (raw)
In-Reply-To: <20191119194658.39af50d0@canb.auug.org.au>
On 11/19/19 12:46 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20191118:
on x86_64:
ERROR: "pm_suspend_target_state" [drivers/gpu/drm/i915/i915.ko] undefined!
# CONFIG_SUSPEND is not set
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2019-11-19 15:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 8:46 linux-next: Tree for Nov 19 Stephen Rothwell
2019-11-19 15:11 ` linux-next: Tree for Nov 19 (kcsan) Randy Dunlap
2019-11-19 16:12 ` Marco Elver
2019-11-19 16:50 ` Randy Dunlap
2019-11-19 18:34 ` Marco Elver
2019-11-19 18:57 ` [PATCH -next] kcsan, ubsan: Make KCSAN+UBSAN work together Marco Elver
2019-11-19 20:16 ` Paul E. McKenney
2019-11-19 21:07 ` Randy Dunlap
2019-11-19 21:17 ` Paul E. McKenney
2019-11-19 19:02 ` linux-next: Tree for Nov 19 (kcsan) Qian Cai
2019-11-19 19:05 ` Marco Elver
2019-11-19 20:14 ` Paul E. McKenney
2019-11-19 15:13 ` linux-next: Tree for Nov 19 (bpf) Randy Dunlap
2019-11-27 23:45 ` linux-next: Tree for Nov 19 (bpf/btf) Randy Dunlap
2019-11-19 15:33 ` Randy Dunlap [this message]
2019-11-20 16:15 ` [Intel-gfx] linux-next: Tree for Nov 19 (i915) Jani Nikula
2019-11-20 16:56 ` Chris Wilson
2019-11-20 21:54 ` Randy Dunlap
2019-11-19 15:38 ` linux-next: Tree for Nov 19 (objtool) Randy Dunlap
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=1d30acd4-9947-d228-967f-c4e76ebca832@infradead.org \
--to=rdunlap@infradead.org \
--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=sfr@canb.auug.org.au \
/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).