All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] linux-next: Tree for Nov 19 (i915)
Date: Wed, 20 Nov 2019 18:15:08 +0200	[thread overview]
Message-ID: <87k17uwmlv.fsf@intel.com> (raw)
In-Reply-To: <1d30acd4-9947-d228-967f-c4e76ebca832@infradead.org>

On Tue, 19 Nov 2019, Randy Dunlap <rdunlap@infradead.org> wrote:
> 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

a70a9e998e8e ("drm/i915: Defer rc6 shutdown to suspend_late")

-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] linux-next: Tree for Nov 19 (i915)
Date: Wed, 20 Nov 2019 18:15:08 +0200	[thread overview]
Message-ID: <87k17uwmlv.fsf@intel.com> (raw)
Message-ID: <20191120161508.bu-GakLepINl8kdE2EOJywGqgdY2FKTAI87-NccwloE@z> (raw)
In-Reply-To: <1d30acd4-9947-d228-967f-c4e76ebca832@infradead.org>

On Tue, 19 Nov 2019, Randy Dunlap <rdunlap@infradead.org> wrote:
> 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

a70a9e998e8e ("drm/i915: Defer rc6 shutdown to suspend_late")

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] linux-next: Tree for Nov 19 (i915)
Date: Wed, 20 Nov 2019 18:15:08 +0200	[thread overview]
Message-ID: <87k17uwmlv.fsf@intel.com> (raw)
Message-ID: <20191120161508.ubyqm6oO_JW1hO_j1IWH7veizca7HYbTWf6q-RC1yxw@z> (raw)
In-Reply-To: <1d30acd4-9947-d228-967f-c4e76ebca832@infradead.org>

On Tue, 19 Nov 2019, Randy Dunlap <rdunlap@infradead.org> wrote:
> 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

a70a9e998e8e ("drm/i915: Defer rc6 shutdown to suspend_late")

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-11-20 16:15 UTC|newest]

Thread overview: 30+ 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 ` linux-next: Tree for Nov 19 (i915) Randy Dunlap
2019-11-19 15:33   ` [Intel-gfx] " Randy Dunlap
2019-11-19 15:33   ` Randy Dunlap
2019-11-19 15:33   ` Randy Dunlap
2019-11-20 16:15   ` Jani Nikula [this message]
2019-11-20 16:15     ` [Intel-gfx] " Jani Nikula
2019-11-20 16:15     ` Jani Nikula
2019-11-20 16:56     ` Chris Wilson
2019-11-20 16:56       ` Chris Wilson
2019-11-20 16:56       ` Chris Wilson
2019-11-20 21:54       ` Randy Dunlap
2019-11-20 21:54         ` Randy Dunlap
2019-11-20 21:54         ` Randy Dunlap
2019-11-19 15:38 ` linux-next: Tree for Nov 19 (objtool) Randy Dunlap
2019-11-20 23:14 ` ✗ Fi.CI.BUILD: failure for linux-next: Tree for Nov 19 (i915) Patchwork
2019-11-20 23:14   ` [Intel-gfx] " Patchwork

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=87k17uwmlv.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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=rdunlap@infradead.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 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.