All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	Peter Griffin <peter.griffin@linaro.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hugues Fruchet <hugues.fruchet@st.com>,
	Loic Pallardy <loic.pallardy@st.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH] rpmsg: Solve circular dependencies involving RPMSG_VIRTIO
Date: Tue, 27 Jun 2017 09:29:19 +0200	[thread overview]
Message-ID: <CAK8P3a0d69ZkVPtHnmLpMf2uft=XX8CyftPKizGuowJZcQv=zQ@mail.gmail.com> (raw)
In-Reply-To: <20170627064309.16507-1-bjorn.andersson@linaro.org>

On Tue, Jun 27, 2017 at 8:43 AM, Bjorn Andersson
<bjorn.andersson@linaro.org> wrote:
> While it's very common to use RPMSG for communicating with firmware
> running on these remoteprocs there is no functional dependency on RPMSG.
> As such RPMSG should be selected by the system integrator and not
> automatically by the remoteproc drivers.
>
> This does solve problems reported with circular Kconfig dependencies for
> Davinci and Keystone remoteproc drivers.
>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---

Looks good to me,

Acked-by: Arnd Bergmann <arnd@arndb.de>

  reply	other threads:[~2017-06-27  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27  6:43 [PATCH] rpmsg: Solve circular dependencies involving RPMSG_VIRTIO Bjorn Andersson
2017-06-27  7:29 ` Arnd Bergmann [this message]
2017-06-27 19:08 ` Suman Anna
2017-06-27 19:08   ` Suman Anna
2017-06-27 21:47   ` Bjorn Andersson
2017-06-27 23:16     ` Suman Anna
2017-06-27 23:16       ` Suman Anna

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='CAK8P3a0d69ZkVPtHnmLpMf2uft=XX8CyftPKizGuowJZcQv=zQ@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=hugues.fruchet@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=loic.pallardy@st.com \
    --cc=mchehab@kernel.org \
    --cc=ohad@wizery.com \
    --cc=peter.griffin@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.