From: Javier Martinez Canillas <javierm@redhat.com>
To: YueHaibing <yuehaibing@huawei.com>,
airlied@linux.ie, daniel@ffwll.ch, maxime@cerno.tech
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH -next] drm/solomon: Make DRM_SSD130X depends on MMU
Date: Wed, 16 Mar 2022 16:18:01 +0100 [thread overview]
Message-ID: <0fa87883-829d-93d0-f0f3-7d3faa8d060c@redhat.com> (raw)
In-Reply-To: <08e81f07-99d2-62a3-8eea-b2c0432b4d18@redhat.com>
On 3/15/22 10:18, Javier Martinez Canillas wrote:
> Hello YueHaibing,
>
> Thanks for the patch.
>
> On 3/12/22 07:34, YueHaibing wrote:
>> WARNING: unmet direct dependencies detected for DRM_GEM_SHMEM_HELPER
>> Depends on [n]: HAS_IOMEM [=y] && DRM [=m] && MMU [=n]
>> Selected by [m]:
>> - DRM_SSD130X [=m] && HAS_IOMEM [=y] && DRM [=m]
>>
>> DRM_GEM_SHMEM_HELPER depends on MMU, DRM_SSD130X should also depends on MMU.
>>
>> Fixes: a61732e80867 ("drm: Add driver for Solomon SSD130x OLED displays")
>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>> ---
>
> Indeed. All the DRM drivers that select DRM_GEM_SHMEM_HELPER depend on MMU.
>
> Acked-by: Javier Martinez Canillas <javierm@redhat.com>
>
Pushed to drm-misc (drm-misc-next). Thanks!
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-03-16 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 6:34 [PATCH -next] drm/solomon: Make DRM_SSD130X depends on MMU YueHaibing
2022-03-12 6:34 ` YueHaibing
2022-03-15 9:18 ` Javier Martinez Canillas
2022-03-16 15:18 ` Javier Martinez Canillas [this message]
2022-04-11 13:49 ` Geert Uytterhoeven
2022-04-11 13:49 ` Geert Uytterhoeven
2022-04-13 7:57 ` Daniel Vetter
2022-04-13 7:57 ` Daniel Vetter
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=0fa87883-829d-93d0-f0f3-7d3faa8d060c@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=yuehaibing@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.