linux-remoteproc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
	kvm@vger.kernel.org
Cc: linux-remoteproc@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	sound-open-firmware@alsa-project.org,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>
Subject: Re: [Sound-open-firmware] [PATCH 5/6] vhost: add an rpmsg API
Date: Sat, 16 May 2020 12:00:35 -0500	[thread overview]
Message-ID: <9737e3f2-e59c-0174-9254-a2d8f29f30b7@linux.intel.com> (raw)
In-Reply-To: <20200516101109.2624-6-guennadi.liakhovetski@linux.intel.com>


> +config VHOST_RPMSG
> +	tristate
> +	depends on VHOST

depends on RPMSG_VIRTIO?

> +	default n

not needed



  reply	other threads:[~2020-05-16 17:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 10:11 [PATCH 0/6] Add a vhost RPMsg API Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 1/6] vhost: convert VHOST_VSOCK_SET_RUNNING to a generic ioctl Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 2/6] vhost: (cosmetic) remove a superfluous variable initialisation Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 3/6] rpmsg: move common structures and defines to headers Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 4/6] rpmsg: update documentation Guennadi Liakhovetski
2020-05-16 10:11 ` [PATCH 5/6] vhost: add an rpmsg API Guennadi Liakhovetski
2020-05-16 17:00   ` Pierre-Louis Bossart [this message]
2020-05-25 13:53     ` [Sound-open-firmware] " Guennadi Liakhovetski
2020-05-26 18:30       ` Pierre-Louis Bossart
2020-05-26 18:55         ` Guennadi Liakhovetski
2020-05-26 20:09           ` Pierre-Louis Bossart
2020-05-16 10:11 ` [PATCH 6/6] rpmsg: add a device ID to also bind to the ADSP device Guennadi Liakhovetski

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=9737e3f2-e59c-0174-9254-a2d8f29f30b7@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=guennadi.liakhovetski@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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).