From: Maxime Ripard <maxime@cerno.tech>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: 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>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: linux-next: Tree for Sep 24 (m68k allmodconfig & drm/vc4/)
Date: Fri, 24 Sep 2021 09:48:57 +0200 [thread overview]
Message-ID: <20210924074857.qbwdammzfujk4ozi@gilmour> (raw)
In-Reply-To: <dfd54a2f-d1db-8897-ae49-5c681a99b281@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
Hi
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?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-09-24 7:49 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 [this message]
2021-09-24 8:21 ` Geert Uytterhoeven
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=20210924074857.qbwdammzfujk4ozi@gilmour \
--to=maxime@cerno.tech \
--cc=geert@linux-m68k.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 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).