From: yamada.masahiro@socionext.com (Masahiro Yamada)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] linux/const.h: move UL() macro to include/linux/const.h
Date: Sun, 8 Jan 2017 15:27:40 +0900 [thread overview]
Message-ID: <CAK7LNARMJVpd47L-3VRafZxdaBT09tA4Bq+V2yFAi_X+cCJsGg@mail.gmail.com> (raw)
In-Reply-To: <15496.1483699555@warthog.procyon.org.uk>
Hi.
2017-01-06 19:45 GMT+09:00 David Howells <dhowells@redhat.com>:
> Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
>
>> diff --git a/include/uapi/linux/const.h b/include/uapi/linux/const.h
>> index c872bfd..76fb0f9 100644
>> --- a/include/uapi/linux/const.h
>> +++ b/include/uapi/linux/const.h
>> @@ -1,7 +1,7 @@
>> /* const.h: Macros for dealing with constants. */
>>
>> -#ifndef _LINUX_CONST_H
>> -#define _LINUX_CONST_H
>> +#ifndef _UAPI_LINUX_CONST_H
>> +#define _UAPI_LINUX_CONST_H
>
> You need to be very careful doing this. Some userspace stuff depends on the
> guard macro names on the kernel header files.
Oh...
>> /* Some constant macros are used in both assembler and
>> * C code. Therefore we cannot annotate them always with
>> @@ -21,7 +21,10 @@
>> #define _AT(T,X) ((T)(X))
>> #endif
>>
>> +#define _UL(x) (_AC(x, UL))
>> +#define _ULL(x) (_AC(x, ULL))
>
> How likely is this to collide with existing userspace code somewhere? It
> looks like the sort of thing that could collide with a C library.
Sorry, I do not have enough insight to answer your questions.
Andrew,
If this seems dangerous, please feel free to drop the entire series
because it is not adding any value except some cleanups.
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2017-01-08 6:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 2:20 [PATCH v2 0/4] linux/const.h: cleanups of macros such as UL(), _BITUL(), BIT() etc Masahiro Yamada
2017-01-05 2:20 ` [PATCH v2 1/4] m68k: rename UL() to TO_UL() Masahiro Yamada
2017-01-05 2:20 ` [PATCH v2 2/4] linux/const.h: move UL() macro to include/linux/const.h Masahiro Yamada
2017-01-05 11:18 ` Catalin Marinas
2017-01-05 11:24 ` Russell King - ARM Linux
2017-01-05 2:20 ` [PATCH v2 3/4] linux/const.h: refactor _BITUL and _BITULL a bit Masahiro Yamada
2017-01-05 2:20 ` [PATCH v2 4/4] linux/const.h: move BIT(_ULL) to linux/const.h for use in assembly Masahiro Yamada
2017-01-06 10:45 ` [PATCH v2 2/4] linux/const.h: move UL() macro to include/linux/const.h David Howells
2017-01-08 6:27 ` Masahiro Yamada [this message]
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=CAK7LNARMJVpd47L-3VRafZxdaBT09tA4Bq+V2yFAi_X+cCJsGg@mail.gmail.com \
--to=yamada.masahiro@socionext.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).