[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdWieEsVUuGT9_jG92=PFssihNxtx-+k50cGEUu=10fs4A@mail.gmail.com>
Date: Fri, 24 Sep 2021 10:21:52 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Maxime Ripard <maxime@...no.tech>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Sep 24 (m68k allmodconfig & drm/vc4/)
Hi Maxime,
On Fri, Sep 24, 2021 at 9:49 AM Maxime Ripard <maxime@...no.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@...ux-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
Powered by blists - more mailing lists