linux-kernel - Re: [PATCH v6 2/2] hwspinlock: qcom: Add support for Qualcomm HW Mutex block

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150318194115.GE491@linaro.org>
Date:	Wed, 18 Mar 2015 13:41:15 -0600
From:	Lina Iyer <lina.iyer@...aro.org>
To:	Bjorn Andersson <bjorn.andersson@...ymobile.com>
Cc:	Ohad Ben-Cohen <ohad@...ery.com>,
	"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
	Jeffrey Hugo <jhugo@...eaurora.org>,
	Suman Anna <s-anna@...com>, Andy Gross <agross@...eaurora.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 2/2] hwspinlock: qcom: Add support for Qualcomm HW
 Mutex block

On Wed, Mar 18 2015 at 10:12 -0600, Bjorn Andersson wrote:
>On Thu 12 Mar 15:29 PDT 2015, Lina Iyer wrote:
>
>> On Fri, Feb 27 2015 at 15:30 -0700, Bjorn Andersson wrote:
>> >Add driver for Qualcomm Hardware Mutex block found in many Qualcomm
>> >SoCs.
>> >
>> >Based on initial effort by Kumar Gala <galak@...eaurora.org>
>> >
>> >Signed-off-by: Bjorn Andersson <bjorn.andersson@...ymobile.com>
>> >+config HWSPINLOCK_QCOM
>> >+	tristate "Qualcomm Hardware Spinlock device"
Any reason, why this is tristate and not a bool?

>> >+	depends on ARCH_QCOM
>> >+	select HWSPINLOCK
>>
>> select MFD_SYSCON as well, perhaps?
>> We seem to be dependent on it.
>>
>
>Right, missed that. Thanks!
>
>Will resend with that addition.
>
>Regards,
>Bjorn
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/