public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Helen Koike <helen.koike@collabora.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>,
	linux-media <linux-media@vger.kernel.org>,
	Zhang Xiaoxu <zhangxiaoxu5@huawei.com>
Subject: Re: linux-next: Tree for Feb 18 (drivers/staging/media/rkisp1/)
Date: Tue, 18 Feb 2020 09:49:29 -0300	[thread overview]
Message-ID: <ad73d63c-1a33-7e47-ba88-1877cc106359@collabora.com> (raw)
In-Reply-To: <e9a420e2-992e-c358-5524-567a10955536@infradead.org>

Hi,

On 2/18/20 3:31 AM, Randy Dunlap wrote:
> On 2/17/20 8:28 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20200217:
>>
> 
> on i386:
> 
> when CONFIG_OF is not set/enabled:
> 
> WARNING: unmet direct dependencies detected for PHY_ROCKCHIP_DPHY_RX0
>   Depends on [n]: STAGING [=y] && STAGING_MEDIA [=y] && MEDIA_SUPPORT [=y] && (ARCH_ROCKCHIP || COMPILE_TEST [=y]) && OF [=n]
>   Selected by [y]:
>   - VIDEO_ROCKCHIP_ISP1 [=y] && STAGING [=y] && STAGING_MEDIA [=y] && MEDIA_SUPPORT [=y] && VIDEO_V4L2 [=y] && VIDEO_V4L2_SUBDEV_API [=y] && (ARCH_ROCKCHIP || COMPILE_TEST [=y])
> 
> 
> Full randconfig file is attached.
> 

Thanks for reporting.

There is a patch on the mailing list fixing this already https://patchwork.linuxtv.org/patch/61175/
Changes were requested (+Zhang Xiaoxu).

Zhang, could you send another version of the patch? Or let me know if I can continue your work.

Thanks
Helen

  reply	other threads:[~2020-02-18 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18  4:28 linux-next: Tree for Feb 18 Stephen Rothwell
2020-02-18  6:31 ` linux-next: Tree for Feb 18 (drivers/staging/media/rkisp1/) Randy Dunlap
2020-02-18 12:49   ` Helen Koike [this message]
2020-02-18  7:04 ` linux-next: Tree for Feb 18 (sound/soc/codecs/wm5110.c) Randy Dunlap
2020-02-18  7:05   ` Randy Dunlap
2020-02-18 10:09     ` Charles Keepax
2020-02-18 11:31       ` Mark Brown
2020-02-18 13:09         ` Charles Keepax

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=ad73d63c-1a33-7e47-ba88-1877cc106359@collabora.com \
    --to=helen.koike@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=zhangxiaoxu5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox