From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Ralf Baechle <ralf@linux-mips.org>,
Chris Metcalf <cmetcalf@tilera.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, Chris Zankel <chris@zankel.net>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] config: simplify INLINE_SPIN_UNLOCK
Date: Fri, 23 Mar 2012 11:54:10 +0530 [thread overview]
Message-ID: <4F6C170A.4070305@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120322095502.30866.75756.sendpatchset@codeblue>
On 03/22/2012 03:25 PM, Raghavendra K T wrote:
> From: Raghavendra K T<raghavendra.kt@linux.vnet.ibm.com>
>
> Patch simplifies current INLINE_SPIN_UNLOCK. compile tested on x86_64
>
> Change log:
> get rid of INLINE_SPIN_UNLOCK entirely replacing it with UNINLINE_SPIN_UNLOCK
> instead with the reverse meaning.
>
> whover wants to uninline the spinlocks (like spinlock debugging, paravirt etc
> all just do select UNINLINE_SPIN_UNLOCK
typo:
Whoever wants to uninline the spinlocks (like spinlock debugging,
paravirt etc) just do select UNINLINE_SPIN_UNLOCK.
>
> Suggested-by: Linus Torvalds<torvalds@linux-foundation.org>
> Signed-off-by: Raghavendra K T<raghavendra.kt@linux.vnet.ibm.com>
> ---
> Please refer : https://lkml.org/lkml/2012/3/21/357
Linus, Please let me know if this is what you were looking for or Did I
really mess it up :(
next prev parent reply other threads:[~2012-03-23 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 9:55 [PATCH 1/1] config: simplify INLINE_SPIN_UNLOCK Raghavendra K T
2012-03-23 6:24 ` Raghavendra K T [this message]
2012-03-23 8:43 ` Ingo Molnar
2012-03-23 15:53 ` Linus Torvalds
2012-03-23 19:44 ` [tip:x86/urgent] locking/kconfig: Simplify INLINE_SPIN_UNLOCK usage tip-bot for Raghavendra K T
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=4F6C170A.4070305@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=chris@zankel.net \
--cc=cmetcalf@tilera.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.