From: ohad@wizery.com (Ohad Ben-Cohen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] hwspinlock: depend on OMAP4
Date: Fri, 18 Mar 2011 10:01:11 +0200 [thread overview]
Message-ID: <mailman.175.1300435625.1530.linux-arm-kernel@lists.infradead.org> (raw)
Currently only OMAP4 supports hwspinlocks, so don't bother asking
anyone else.
Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
---
drivers/hwspinlock/Kconfig | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/hwspinlock/Kconfig b/drivers/hwspinlock/Kconfig
index eb4af28..1f29bab 100644
--- a/drivers/hwspinlock/Kconfig
+++ b/drivers/hwspinlock/Kconfig
@@ -4,6 +4,7 @@
config HWSPINLOCK
tristate "Generic Hardware Spinlock framework"
+ depends on ARCH_OMAP4
help
Say y here to support the generic hardware spinlock framework.
You only need to enable this if you have hardware spinlock module
--
1.7.1
--0016e6d2722740c2ce049ebd4387
Content-Type: text/x-patch; charset=US-ASCII; name="0001-hwspinlock-depend-on-OMAP4.patch"
Content-Disposition: attachment;
filename="0001-hwspinlock-depend-on-OMAP4.patch"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_gletqugf0
RnJvbSBkMDg2ZThmOTk0YjkyNzJmOGM5OTlhZjBhNGQzMmQ4NzA3NDljNzdhIE1vbiBTZXAgMTcg
MDA6MDA6MDAgMjAwMQpGcm9tOiBPaGFkIEJlbi1Db2hlbiA8b2hhZEB3aXplcnkuY29tPgpEYXRl
OiBGcmksIDE4IE1hciAyMDExIDEwOjAxOjExICswMjAwClN1YmplY3Q6IFtQQVRDSF0gaHdzcGlu
bG9jazogZGVwZW5kIG9uIE9NQVA0CgpDdXJyZW50bHkgb25seSBPTUFQNCBzdXBwb3J0cyBod3Nw
aW5sb2Nrcywgc28gZG9uJ3QgYm90aGVyIGFza2luZwphbnlvbmUgZWxzZS4KClNpZ25lZC1vZmYt
Ynk6IE9oYWQgQmVuLUNvaGVuIDxvaGFkQHdpemVyeS5jb20+Ci0tLQogZHJpdmVycy9od3NwaW5s
b2NrL0tjb25maWcgfCAgICAxICsKIDEgZmlsZXMgY2hhbmdlZCwgMSBpbnNlcnRpb25zKCspLCAw
IGRlbGV0aW9ucygtKQoKZGlmZiAtLWdpdCBhL2RyaXZlcnMvaHdzcGlubG9jay9LY29uZmlnIGIv
ZHJpdmVycy9od3NwaW5sb2NrL0tjb25maWcKaW5kZXggZWI0YWYyOC4uMWYyOWJhYiAxMDA2NDQK
LS0tIGEvZHJpdmVycy9od3NwaW5sb2NrL0tjb25maWcKKysrIGIvZHJpdmVycy9od3NwaW5sb2Nr
L0tjb25maWcKQEAgLTQsNiArNCw3IEBACiAKIGNvbmZpZyBIV1NQSU5MT0NLCiAJdHJpc3RhdGUg
IkdlbmVyaWMgSGFyZHdhcmUgU3BpbmxvY2sgZnJhbWV3b3JrIgorCWRlcGVuZHMgb24gQVJDSF9P
TUFQNAogCWhlbHAKIAkgIFNheSB5IGhlcmUgdG8gc3VwcG9ydCB0aGUgZ2VuZXJpYyBoYXJkd2Fy
ZSBzcGlubG9jayBmcmFtZXdvcmsuCiAJICBZb3Ugb25seSBuZWVkIHRvIGVuYWJsZSB0aGlzIGlm
IHlvdSBoYXZlIGhhcmR3YXJlIHNwaW5sb2NrIG1vZHVsZQotLSAKMS43LjEKCg==
--0016e6d2722740c2ce049ebd4387--
reply other threads:[~2011-03-18 8:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.175.1300435625.1530.linux-arm-kernel@lists.infradead.org \
--to=ohad@wizery.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).