linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 24 (m68k allmodconfig & drm/vc4/)
Date: Fri, 24 Sep 2021 10:21:52 +0200	[thread overview]
Message-ID: <CAMuHMdWieEsVUuGT9_jG92=PFssihNxtx-+k50cGEUu=10fs4A@mail.gmail.com> (raw)
In-Reply-To: <20210924074857.qbwdammzfujk4ozi@gilmour>

Hi Maxime,

On Fri, Sep 24, 2021 at 9:49 AM Maxime Ripard <maxime@cerno.tech> wrote:
> On Thu, Sep 23, 2021 at 10:54:49PM -0700, Randy Dunlap wrote:
> > On 9/23/21 9:54 PM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20210923:
> > >
> >
> > from commit 36e9bcb8edfc in linux-next:
> >
> >
> > m68k allmodconfig:
> >
> > WARNING: unmet direct dependencies detected for PM
> >   Depends on [n]: !MMU [=y]
> >   Selected by [m]:
> >   - DRM_VC4 [=m] && HAS_IOMEM [=y] && (ARCH_BCM || ARCH_BCM2835 || COMPILE_TEST [=y]) && DRM [=m] && SND [=m] && SND_SOC [=m] && COMMON_CLK [=y]
>
> I don't really know how to fix this one, should we move that select to
> the ARCH_* symbol, or something else?

You cannot select PM from drivers, only from platform symbols, as the
former lack the knowledge if the platform supports PM or not.

IIf it builds without PM, drop the select.
If it does not build without PM, add a dependency on PM.

Do ARCH_BCM || ARCH_BCM2835 always imply PM?

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-09-24  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24  4:54 linux-next: Tree for Sep 24 Stephen Rothwell
2021-09-24  5:54 ` linux-next: Tree for Sep 24 (m68k allmodconfig & drm/vc4/) Randy Dunlap
2021-09-24  7:48   ` Maxime Ripard
2021-09-24  8:21     ` Geert Uytterhoeven [this message]
2021-09-24 15:51 ` linux-next: Tree for Sep 24 (scsi/ufs) 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='CAMuHMdWieEsVUuGT9_jG92=PFssihNxtx-+k50cGEUu=10fs4A@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --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 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).