From: YueHaibing <yuehaibing@huawei.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
<linux-arm-msm@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Tree for May 16 (drm/msm: kconfig warning)
Date: Tue, 17 May 2022 15:51:58 +0800 [thread overview]
Message-ID: <65ec4f4f-5fba-73eb-e73c-81366d94ac0b@huawei.com> (raw)
In-Reply-To: <e61b5844-2595-4138-bf64-5b4d48ec8a4f@infradead.org>
On 2022/5/16 23:10, Randy Dunlap wrote:
>
> On 5/16/22 03:57, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20220513:
>>
>
> on i386 or x86_64:
>
> WARNING: unmet direct dependencies detected for DRM_DP_AUX_BUS
> Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && OF [=n]
> Selected by [y]:
> - DRM_MSM [=y] && HAS_IOMEM [=y] && DRM [=y] && (ARCH_QCOM || SOC_IMX5 || COMPILE_TEST [=y]) && COMMON_CLK [=y] && IOMMU_SUPPORT [=y] && (QCOM_OCMEM [=n] || QCOM_OCMEM [=n]=n) && (QCOM_LLCC [=n] || QCOM_LLCC [=n]=n) && (QCOM_COMMAND_DB [=n] || QCOM_COMMAND_DB [=n]=n)
This is fixed by
https://www.spinics.net/lists/kernel/msg4349168.html
>
>
> Full randconfig file is attached.
>
next prev parent reply other threads:[~2022-05-17 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 10:57 linux-next: Tree for May 16 Stephen Rothwell
2022-05-16 15:10 ` linux-next: Tree for May 16 (drm/msm: kconfig warning) Randy Dunlap
2022-05-17 7:51 ` YueHaibing [this message]
2022-05-16 21:22 ` linux-next: Tree for May 16 (drm/i915/gt/intel_gt_sysfs_pm.c) Randy Dunlap
2022-05-17 7:35 ` Tvrtko Ursulin
2022-05-17 18:12 ` 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=65ec4f4f-5fba-73eb-e73c-81366d94ac0b@huawei.com \
--to=yuehaibing@huawei.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=rdunlap@infradead.org \
--cc=robdclark@gmail.com \
--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).