netdev - Re: [PATCH 1/2] net wireless wcn36xx add wcnss platform code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87iofanu9s.fsf@kamboji.qca.qualcomm.com>
Date:	Tue, 10 Feb 2015 08:41:03 +0200
From:	Kalle Valo <kvalo@...eaurora.org>
To:	Bjorn Andersson <bjorn@...o.se>
Cc:	Andy Green <andy.green@...aro.org>,
	Eugene Krasnikov <k.eugene.e@...il.com>,
	wcn36xx <wcn36xx@...ts.infradead.org>,
	linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] net wireless wcn36xx add wcnss platform code

Bjorn Andersson <bjorn@...o.se> writes:

> On Sat, Jan 17, 2015 at 9:16 PM, Andy Green <andy.green@...aro.org> wrote:
>> From: Eugene Krasnikov <k.eugene.e@...il.com>
>>
>> AG modified to remove regulator handling not needed on msm8916-qrd
>>
>> Signed-off-by: Eugene Krasnikov <k.eugene.e@...il.com>
>> Signed-off-by: Andy Green <andy.green@...aro.org>
>> ---
>>  drivers/net/wireless/ath/wcn36xx/Makefile      |    2
>>  drivers/net/wireless/ath/wcn36xx/wcn36xx-msm.c |  357 ++++++++++++++++++++++++
>
> It seems like we're finally getting somewhere with the hwspinlock
> devicetree binding, which will allow us to go ahead with the work on
> getting smem, smd, smsm and smp2p into mainline.
>
> With that in place we have fixed apis that this driver will run upon,
> so I would like to suggest that we at that point fold this logic into
> the driver itself rather than having this skim.

Yeah, this approach would be much better.

-- 
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html