From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
To: David Rientjes <rientjes@google.com>
Cc: arnd@arndb.de, akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cleanup include/asm-generic/atomic.h
Date: Tue, 22 Jul 2014 09:27:23 +0530 [thread overview]
Message-ID: <53CDE123.6040100@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1407211707510.5825@chino.kir.corp.google.com>
On Tuesday 22 July 2014 05:38 AM, David Rientjes wrote:
> On Tue, 22 Jul 2014, Madhavan Srinivasan wrote:
>
>> Commit 4b358e2206 "cleanup include/asm-generic/atomic.h" added
>> comments for #else/#endif, but ended up adding same comment
>> "BITS_PER_LONG == 64" on both sides. This patch fixes it.
>>
>
> It's intentionally like that, it comments the condition for which the
> #endif is matched.
Ok, will change the else comment. And include/asm-generic/local64.h
also needs a change in comment.
Regards
Maddy
>
>> Signed-off-by: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
>> ---
>> include/asm-generic/atomic-long.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/asm-generic/atomic-long.h b/include/asm-generic/atomic-long.h
>> index b7babf0..a8434c6 100644
>> --- a/include/asm-generic/atomic-long.h
>> +++ b/include/asm-generic/atomic-long.h
>> @@ -253,6 +253,6 @@ static inline long atomic_long_add_unless(atomic_long_t *l, long a, long u)
>> #define atomic_long_xchg(v, new) \
>> (atomic_xchg((atomic_t *)(v), (new)))
>>
>> -#endif /* BITS_PER_LONG == 64 */
>> +#endif /* BITS_PER_LONG != 64 */
>>
>> #endif /* _ASM_GENERIC_ATOMIC_LONG_H */
>
next prev parent reply other threads:[~2014-07-22 3:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 23:30 [PATCH] cleanup include/asm-generic/atomic.h Madhavan Srinivasan
2014-07-22 0:08 ` David Rientjes
2014-07-22 3:57 ` Madhavan Srinivasan [this message]
2014-07-22 22:17 ` David Rientjes
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=53CDE123.6040100@linux.vnet.ibm.com \
--to=maddy@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
/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