From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vinod Koul <vinod.koul@intel.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Griffin <peter.griffin@linaro.org>
Subject: Re: linux-next: manual merge of the rpmsg tree with the slave-dma tree
Date: Wed, 16 Nov 2016 22:40:59 -0800 [thread overview]
Message-ID: <20161117064059.GF28340@tuxbot> (raw)
In-Reply-To: <20161114162026.0511e0db@canb.auug.org.au>
On Sun 13 Nov 21:20 PST 2016, Stephen Rothwell wrote:
> Hi Bjorn,
>
Hi Stephen,
> Today's linux-next merge of the rpmsg tree got a conflict in:
>
> drivers/remoteproc/Kconfig
>
> between commit:
>
> bb6869b21478 ("remoteproc: st_slim_rproc: add a slimcore rproc driver")
>
> from the slave-dma tree and commit:
>
> 99d93470dcb4 ("remoteproc: qcom_wcnss: Fix circular module dependency")
>
> from the rpmsg tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
Thanks for the fix and the report of the dependency issue of
QCOM_ADSP_PIL.
I have merged the problematic topic branch from Vinod into my tree and
fixed up the discrepancies. So you should be able to drop this
workaround and you should not see the ADSP issue.
Regards,
Bjorn
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc drivers/remoteproc/Kconfig
> index 14d5d2d43a38,5fcbefcb8636..000000000000
> --- a/drivers/remoteproc/Kconfig
> +++ b/drivers/remoteproc/Kconfig
> @@@ -100,10 -95,9 +96,9 @@@ config QCOM_WCNSS_PI
> tristate "Qualcomm WCNSS Peripheral Image Loader"
> depends on OF && ARCH_QCOM
> depends on QCOM_SMEM
> + depends on REMOTEPROC
> select QCOM_MDT_LOADER
> select QCOM_SCM
> - select QCOM_WCNSS_IRIS
> - select REMOTEPROC
> help
> Say y here to support the Peripheral Image Loader for the Qualcomm
> Wireless Connectivity Subsystem.
prev parent reply other threads:[~2016-11-17 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 5:20 linux-next: manual merge of the rpmsg tree with the slave-dma tree Stephen Rothwell
2016-11-17 6:40 ` Bjorn Andersson [this message]
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=20161117064059.GF28340@tuxbot \
--to=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=sfr@canb.auug.org.au \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).