linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: moudy ho <moudy.ho@mediatek.com>,
	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>,
	"linux-mediatek@lists.infradead.org" 
	<linux-mediatek@lists.infradead.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: linux-next: Tree for Sep 1 (Kconfig for VIDEO_MEDIATEK_VPU)
Date: Thu, 1 Sep 2022 20:26:24 -0700	[thread overview]
Message-ID: <a8ac77b7-60a9-3e62-0d07-fa03c5600740@infradead.org> (raw)
In-Reply-To: <e213e9d8ef900db665fee08b484181e1d47c5171.camel@mediatek.com>



On 9/1/22 19:55, moudy ho wrote:
> Hi Randy,
> 
> Thanks for your efforts on this matter, the warning is due to not
> setting V4L_MEM2MEM_DRIVERS on defconfig which the VIDEO_MEDIATEK_VPU
> depends.
> Could I send a patch to add a V4L_MEM2MEM_DRIVERS selection in MDP3
> Kconfig to avoid this warning?
> 
> Regards,
> Moudy

Hi,
That sounds good to me.

Thanks.

> 
> On Thu, 2022-09-01 at 13:38 -0700, Randy Dunlap wrote:
>>
>> On 9/1/22 00:18, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> News: there will be no linux-next releases tomorrow or on Monday.
>>>
>>> Changes since 20220831:
>>>
>>
>> on i386 or x86_64:
>>
>> WARNING: unmet direct dependencies detected for VIDEO_MEDIATEK_VPU
>>   Depends on [n]: MEDIA_SUPPORT [=y] && MEDIA_PLATFORM_SUPPORT [=y]
>> && MEDIA_PLATFORM_DRIVERS [=y] && V4L_MEM2MEM_DRIVERS [=n] &&
>> VIDEO_DEV [=y] && (ARCH_MEDIATEK || COMPILE_TEST [=y])
>>   Selected by [y]:
>>   - VIDEO_MEDIATEK_MDP3 [=y] && MEDIA_SUPPORT [=y] &&
>> MEDIA_PLATFORM_SUPPORT [=y] && MEDIA_PLATFORM_DRIVERS [=y] &&
>> (MTK_IOMMU [=n] || COMPILE_TEST [=y]) && VIDEO_DEV [=y] &&
>> (ARCH_MEDIATEK || COMPILE_TEST [=y]) && HAS_DMA [=y] && REMOTEPROC
>> [=y]
>>
>>
>>
>> Full x86_64 randconfig file is attached.
>>
> 

-- 
~Randy

      reply	other threads:[~2022-09-02  3:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  7:18 linux-next: Tree for Sep 1 Stephen Rothwell
2022-09-01 20:38 ` linux-next: Tree for Sep 1 (Kconfig for VIDEO_MEDIATEK_VPU) Randy Dunlap
2022-09-02  2:55   ` moudy ho
2022-09-02  3:26     ` Randy Dunlap [this message]

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=a8ac77b7-60a9-3e62-0d07-fa03c5600740@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=moudy.ho@mediatek.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).