mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <rdunlap@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	"David S. Miller" <davem@davemloft.net>,
	sparclinux@vger.kernel.org, Kirill Tkhai <tkhai@yandex.ru>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] sparc: allow PM configs for sparc32 COMPILE_TEST
Date: Sun, 5 Feb 2023 09:54:36 +0100	[thread overview]
Message-ID: <Y99uzN8lI/U3Jkxb@ravnborg.org> (raw)
In-Reply-To: <20230205004357.29459-1-rdunlap@infradead.org>

On Sat, Feb 04, 2023 at 04:43:57PM -0800, Randy Dunlap wrote:
> When doing randconfig builds for sparc32 with COMPILE_TEST,
> some (non-Sparc) drivers cause kconfig warnings with the
> Kconfig symbols PM, PM_GENERIC_DOMAINS, or PM_GENERIC_DOMAINS_OF.
> 
> This is due to arch/sparc/Kconfig not using the PM Kconfig for
> Sparc32:
> 
>   if SPARC64
>   source "kernel/power/Kconfig"
>   endif
> 
> Arnd suggested adding "|| COMPILE_TEST" to the conditional,
> instead of trying to track down every driver that selects
> any of these PM symbols.
> 
> Fixes the following kconfig warnings:
...
> 
> Fixes: bdde6b3c8ba4 ("sparc64: Hibernation support")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: sparclinux@vger.kernel.org
> Cc: Kirill Tkhai <tkhai@yandex.ru>
> Cc: Sam Ravnborg <sam@ravnborg.org>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
I hope Andrew picks this up.

	Sam

      reply	other threads:[~2023-02-05  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05  0:43 Randy Dunlap
2023-02-05  8:54 ` Sam Ravnborg [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=Y99uzN8lI/U3Jkxb@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=tkhai@yandex.ru \
    /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®