linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Anup Patel <Anup.Patel@wdc.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
	Anup Patel <anup@brainfault.org>,
	Palmer Dabbelt <palmer@sifive.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Atish Patra <Atish.Patra@wdc.com>,
	Alistair Francis <Alistair.Francis@wdc.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>, Christoph Hellwig <hch@lst.de>
Subject: RE: [PATCH 1/4] RISC-V: Add kconfig option for QEMU virt machine
Date: Mon, 9 Mar 2020 10:24:05 +0000	[thread overview]
Message-ID: <MN2PR04MB60611C6CE40C024E336C8ADC8DFE0@MN2PR04MB6061.namprd04.prod.outlook.com> (raw)
In-Reply-To: <mvmh7yx4z2u.fsf@suse.de>



> -----Original Message-----
> From: Andreas Schwab <schwab@suse.de>
> Sent: 09 March 2020 15:42
> To: Anup Patel <Anup.Patel@wdc.com>
> Cc: Palmer Dabbelt <palmer@sifive.com>; Paul Walmsley
> <paul.walmsley@sifive.com>; Albert Ou <aou@eecs.berkeley.edu>; Atish
> Patra <Atish.Patra@wdc.com>; Alistair Francis <Alistair.Francis@wdc.com>;
> Christoph Hellwig <hch@lst.de>; Anup Patel <anup@brainfault.org>; linux-
> riscv@lists.infradead.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 1/4] RISC-V: Add kconfig option for QEMU virt machine
> 
> WARNING: unmet direct dependencies detected for DRM_VIRTIO_GPU
>   Depends on [m]: HAS_IOMEM [=y] && DRM [=m] && VIRTIO [=y] && MMU
> [=y]
>   Selected by [y]:
>   - SOC_VIRT [=y]
> 
> WARNING: unmet direct dependencies detected for NET_9P_VIRTIO
>   Depends on [m]: NET [=y] && NET_9P [=m] && VIRTIO [=y]
>   Selected by [y]:
>   - SOC_VIRT [=y]

We don't see this warning with rv32_defconfig and defconfig.

Perhaps selecting DRM and NET_9P from SOC_VIRT will help. Can you
try and send patch ?

Regards,
Anup


  reply	other threads:[~2020-03-09 10:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 13:22 [PATCH 0/4] QEMU Virt Machine Kconfig option Anup Patel
2019-11-25 13:22 ` [PATCH 1/4] RISC-V: Add kconfig option for QEMU virt machine Anup Patel
2019-11-26 19:12   ` Atish Patra
2019-12-02 23:32   ` Palmer Dabbelt
2020-03-09 10:11   ` Andreas Schwab
2020-03-09 10:24     ` Anup Patel [this message]
2020-03-10 10:21       ` Andreas Schwab
2020-03-10 11:57         ` Anup Patel
2019-11-25 13:22 ` [PATCH 2/4] RISC-V: Enable QEMU virt machine support in defconfigs Anup Patel
2019-11-26 19:14   ` Atish Patra
2019-12-02 23:32     ` Palmer Dabbelt
2019-12-03  3:06     ` Anup Patel
2019-11-25 13:22 ` [PATCH 3/4] RISC-V: Select SYSCON Reboot and Poweroff for QEMU virt machine Anup Patel
2019-12-02 23:32   ` Palmer Dabbelt
2019-11-25 13:22 ` [PATCH 4/4] RISC-V: Select Goldfish RTC driver " Anup Patel
2019-11-26 19:17   ` Atish Patra
2019-12-02 23:32   ` Palmer Dabbelt
2019-12-02 23:32 ` [PATCH 0/4] QEMU Virt Machine Kconfig option Palmer Dabbelt
2019-12-03  3:03   ` Anup Patel

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=MN2PR04MB60611C6CE40C024E336C8ADC8DFE0@MN2PR04MB6061.namprd04.prod.outlook.com \
    --to=anup.patel@wdc.com \
    --cc=Alistair.Francis@wdc.com \
    --cc=Atish.Patra@wdc.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.com \
    --cc=schwab@suse.de \
    /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).