From: Andy Gross <andy.gross@linaro.org>
To: David Miller <davem@davemloft.net>
Cc: bjorn.andersson@linaro.org, marcel@holtmann.org,
gustavo@padovan.org, johan.hedberg@gmail.com,
k.eugene.e@gmail.com, kvalo@codeaurora.org,
david.brown@linaro.org, arnd@arndb.de,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-soc@vger.kernel.org
Subject: Re: [PATCH 1/3] soc: qcom: smd: Transition client drivers from smd to rpmsg
Date: Wed, 22 Mar 2017 16:56:27 -0500 [thread overview]
Message-ID: <20170322215627.GD22585@hector.attlocal.net> (raw)
In-Reply-To: <20170322.114439.679826829857326050.davem@davemloft.net>
On Wed, Mar 22, 2017 at 11:44:39AM -0700, David Miller wrote:
> From: Bjorn Andersson <bjorn.andersson@linaro.org>
> Date: Mon, 20 Mar 2017 16:35:42 -0700
>
> > By moving these client drivers to use RPMSG instead of the direct SMD
> > API we can reuse them ontop of the newly added GLINK wire-protocol
> > support found in the 820 and 835 Qualcomm platforms.
> >
> > As the new (RPMSG-based) and old SMD implementations are mutually
> > exclusive we have to change all client drivers in one commit, to make
> > sure we have a working system before and after this transition.
> >
> > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> > ---
> >
> > Based on v4.11-rc3 with Arnd's Kconfig dependency fixes for BT_QCOMSMD
> > (https://lkml.org/lkml/2017/3/20/1038).
>
> Just some questions since I'm supposed to merge this into my net-next
> tree.
>
> What is the status of the Kconfig dependency fix and how will I be
> getting it?
>
> Second, should I merge all three of these patches to net-next or just
> this one?
David,
I ack'd all three. Please take these through your tree.
Bjorn,
Are we going to need an immutable branch or tag for sychronizing work?
Regards,
Andy Gross
next prev parent reply other threads:[~2017-03-22 21:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 23:35 [PATCH 1/3] soc: qcom: smd: Transition client drivers from smd to rpmsg Bjorn Andersson
2017-03-20 23:35 ` [PATCH 2/3] soc: qcom: smd: Remove standalone driver Bjorn Andersson
2017-03-22 21:53 ` Andy Gross
2017-03-20 23:35 ` [PATCH 3/3] soc: qcom: smd-rpm: Add msm8996 compatibility Bjorn Andersson
2017-03-22 21:54 ` Andy Gross
2017-03-21 8:20 ` [PATCH 1/3] soc: qcom: smd: Transition client drivers from smd to rpmsg Marcel Holtmann
2017-03-21 12:17 ` Kalle Valo
2017-03-22 18:44 ` David Miller
2017-03-22 19:23 ` Marcel Holtmann
2017-03-23 2:23 ` David Miller
2017-03-22 21:56 ` Andy Gross [this message]
2017-03-22 21:57 ` Bjorn Andersson
2017-03-23 23:56 ` David Miller
2017-03-27 22:58 ` Bjorn Andersson
2017-03-27 23:04 ` David Miller
2017-03-28 5:49 ` Bjorn Andersson
2017-03-29 0:58 ` David Miller
2017-03-22 21:52 ` Andy Gross
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=20170322215627.GD22585@hector.attlocal.net \
--to=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=david.brown@linaro.org \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=k.eugene.e@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=wcn36xx@lists.infradead.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