From: Emil Velikov <emil.l.velikov@gmail.com>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"kernel@stlinux.com" <kernel@stlinux.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"vinod.koul@intel.com" <vinod.koul@intel.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v9 17/19] drm/virtio: kconfig: Fix recursive dependency issue.
Date: Tue, 20 Sep 2016 08:20:48 +0100 [thread overview]
Message-ID: <CACvgo533SrCHV9V_L3_UA8sTPWKyC9HA8k5BqNad+1eaoWPLmA@mail.gmail.com> (raw)
In-Reply-To: <1474277660-5196-2-git-send-email-peter.griffin@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 296 bytes --]
On Monday, 19 September 2016, Peter Griffin <peter.griffin@linaro.org>
wrote:
> ST_SLIM_REMOTEPROC must select REMOTEPROC, which exposes the following
> recursive dependency.
>
> It must not select, it must depend? Did you miss my earlier
question/suggestion that mentions that ?
Regards,
Emil
[-- Attachment #1.2: Type: text/html, Size: 517 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2016-09-20 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 9:34 [PATCH 0/2] Fix recursive Kconfig depedency issue Peter Griffin
2016-09-19 9:34 ` [PATCH 1/2] drm/virtio: kconfig: Fix recursive dependency issue Peter Griffin
2016-09-20 7:20 ` Emil Velikov [this message]
2016-09-20 7:24 ` [PATCH v9 17/19] " Emil Velikov
2016-09-19 9:34 ` [PATCH 2/2] drm/virtio: kconfig: Fixup white space Peter Griffin
-- strict thread matches above, loose matches on Subject: below --
2016-09-05 13:16 [PATCH v9 00/19] Add support for FDMA DMA controller and slim core rproc found on STi chipsets Peter Griffin
2016-09-05 13:16 ` [PATCH v9 17/19] drm/virtio: kconfig: Fix recursive dependency issue Peter Griffin
[not found] ` <1473081421-16555-18-git-send-email-peter.griffin@linaro.org>
2016-09-19 23:18 ` Emil Velikov
2016-09-20 8:32 ` Peter Griffin
2016-09-20 9:33 ` Jani Nikula
2016-09-21 12:09 ` Emil Velikov
[not found] ` <8760pqncee.fsf@intel.com>
2016-10-06 9:37 ` Peter Griffin
2016-10-06 10:45 ` Emil Velikov
[not found] ` <CACvgo50vU5_=KFUCAZDaQPepPdsbnF8KN1b+f6KJNuBW6qRdSg@mail.gmail.com>
2016-10-07 17:44 ` Peter Griffin
[not found] ` <CACvgo53fuoPVjBAkZbWFPVxosObjvxoDgFdR_BkSTgevqyGg9g@mail.gmail.com>
2016-09-27 17:01 ` Bjorn Andersson
2016-10-06 10:10 ` Emil Velikov
2016-10-06 10:48 ` Peter Griffin
2016-10-06 11:31 ` Emil Velikov
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=CACvgo533SrCHV9V_L3_UA8sTPWKyC9HA8k5BqNad+1eaoWPLmA@mail.gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=sfr@canb.auug.org.au \
--cc=vinod.koul@intel.com \
--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).