mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Linux DRI Development <dri-devel@lists.freedesktop.org>,
	Samuel Zhang <guoqing.zhang@amd.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Mario Limonciello <mario.limonciello@amd.com>,
	amd-gfx@lists.freedesktop.org
Subject: Re: linux-next: Tree for Jul 11 [drivers/gpu/drm/amd/amdgpu/amdgpu.ko]
Date: Fri, 11 Jul 2025 14:25:10 -0700	[thread overview]
Message-ID: <49080a96-2c7a-4eea-a64c-deac0b7a665b@infradead.org> (raw)
In-Reply-To: <20250711191014.12a64210@canb.auug.org.au>



On 7/11/25 2:10 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20250710:
> 

on x86_64, when
# CONFIG_SUSPEND is not set
# CONFIG_HIBERNATION is not set
# CONFIG_PM is not set

ERROR: modpost: "pm_hibernate_is_recovering" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!

caused by commit
530694f54dd5e ("drm/amdgpu: do not resume device in thaw for normal hibernation")

Rafael, is a stub appropriate for this case?

-- 
~Randy


  reply	other threads:[~2025-07-11 21:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11  9:10 linux-next: Tree for Jul 11 Stephen Rothwell
2025-07-11 21:25 ` Randy Dunlap [this message]
2025-07-12  8:11   ` linux-next: Tree for Jul 11 [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] Rafael J. Wysocki
2025-07-12 19:02     ` Mario Limonciello
2025-07-13 11:34       ` Rafael J. Wysocki
2025-07-11 22:12 ` linux-next: Tree for Jul 11 (drivers/platform/x86/lenovo/wmi-gamezone.o) Randy Dunlap
2025-07-13 16:06   ` Ilpo Järvinen
2025-07-13  6:49 ` linux-next: Tree for Jul 11 (drivers/gpu/drm/msm/msm_gem.c) Randy Dunlap
2025-07-13 13:16   ` Rob Clark
2025-07-13 17:47     ` 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=49080a96-2c7a-4eea-a64c-deac0b7a665b@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guoqing.zhang@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=rafael@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

all inboxes | Powered by JetHome®