From: Kalle Valo <kvalo@codeaurora.org>
To: Andy Gross <andy.gross@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Eugene Krasnikov <k.eugene.e@gmail.com>,
wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev <netdev@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v4 2/4] wcn36xx: Transition driver to SMD client
Date: Fri, 09 Sep 2016 08:17:09 +0300 [thread overview]
Message-ID: <87inu5r6sq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160909042754.GA32071@hector.attlocal.net> (Andy Gross's message of "Thu, 8 Sep 2016 23:27:54 -0500")
Andy Gross <andy.gross@linaro.org> writes:
>> > >> This doesn't compile for me:
>> > >>
>> > >
>> > > I thought I mentioned this in the mail, sorry for missing that.
>> >
>> > Maybe you did and I just forgot, I have a tendency to do that :)
>> >
>> > > There is a patch for this issue in linux-next already [1] which is
>> > > part of [2], which was part of the pull request to arm-soc for
>> > > inclusion in v4.9.
>> > >
>> > > [1] https://patchwork.kernel.org/patch/9272457/
>> > > [2] https://git.kernel.org/cgit/linux/kernel/git/agross/linux.git/tag/?h=qcom-drivers-for-4.9
>> >
>> > So the commit in question is:
>> >
>> > soc: qcom: smd: Correct compile stub prototypes
>> > https://git.kernel.org/cgit/linux/kernel/git/agross/linux.git/commit/?h=qcom-drivers-for-4.9&id=3a1281848830fcb3202cfd7ffe62d19641471d05
>> >
>>
>> Correct
>>
>> > But that's not obviously in my tree yet, but I should have it after
>> > 4.9-rc1 is released. I think it's easiest that I wait for that before
>> > applying these. Do you agree?
>> >
>>
>> Would be nice to have it land sooner rather than later, but I'm okay
>> with this.
>
> We could just treat the tag as immutable. You can merge the tag in and arm-soc
> can as well. it'll just get nop'd the second time it is taken. The only
> downside is if arm-soc doesn't take my merge request.
I take it that you are talking about this tag:
git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git qcom-drivers-for-4.9
I did a test pull and there are only 8 commits so in theory that could
work. But my trees go via Dave Miller's net-next so I can't control when
they hit Linus' tree. It might be that Linus pulls the net-next tree
before arm-soc and arm-soc commits coming from net-next might confuse
people. I'm just afraid that the hassle would outweight the benefit.
> Or we can wait till -rc1
To keep things simple I prefer this option. Of course it means waiting
few more extra weeks, but when working with new subsystems that can
happen. The crystall ball[1] says that 4.9-rc1 would be released on
2016-10-16 so it's not that far away.
[1] http://phb-crystal-ball.org/
--
Kalle Valo
next prev parent reply other threads:[~2016-09-09 5:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 22:18 [PATCH v4 1/4] soc: qcom: wcnss_ctrl: Stub wcnss_ctrl API Bjorn Andersson
2016-09-06 22:18 ` [PATCH v4 2/4] wcn36xx: Transition driver to SMD client Bjorn Andersson
2016-09-07 11:35 ` Kalle Valo
2016-09-08 12:16 ` Kalle Valo
2016-09-08 15:31 ` Bjorn Andersson
2016-09-08 17:35 ` Kalle Valo
2016-09-09 4:21 ` Bjorn Andersson
2016-09-09 4:27 ` Andy Gross
2016-09-09 5:17 ` Kalle Valo [this message]
2016-09-06 22:18 ` [PATCH v4 3/4] wcn36xx: Implement firmware assisted scan Bjorn Andersson
2016-09-06 22:18 ` [PATCH v4 4/4] wcn36xx: Implement print_reg indication Bjorn Andersson
2016-09-06 23:12 ` [PATCH v4 1/4] soc: qcom: wcnss_ctrl: Stub wcnss_ctrl API Marcel Holtmann
2016-09-07 1:39 ` Andy Gross
2016-09-07 11:33 ` Kalle Valo
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=87inu5r6sq.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=k.eugene.e@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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
Powered by JetHome