From: Michael Ellerman <mpe@ellerman.id.au>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v1 1/1] powerpc/prom_init: Move custom isspace() to its own namespace
Date: Wed, 09 Jun 2021 17:00:16 +1000 [thread overview]
Message-ID: <87o8cfed4v.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <YL5Tm7jZaaQ0POH5@smile.fi.intel.com>
Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
> On Mon, May 10, 2021 at 05:49:25PM +0300, Andy Shevchenko wrote:
>> If by some reason any of the headers will include ctype.h
>> we will have a name collision. Avoid this by moving isspace()
>> to the dedicate namespace.
>>
>> First appearance of the code is in the commit cf68787b68a2
>> ("powerpc/prom_init: Evaluate mem kernel parameter for early allocation").
>
> Any comments on this?
Looks fine. Thanks.
I just missed it because it came in a bit early, I tend not to pick
things up until rc2.
I tweaked the formatting of prom_isxdigit() slightly now that we allow
100 column lines.
Have put it in my next-test now.
cheers
>> diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
>> index 41ed7e33d897..6845cbbc0cd4 100644
>> --- a/arch/powerpc/kernel/prom_init.c
>> +++ b/arch/powerpc/kernel/prom_init.c
>> @@ -701,13 +701,13 @@ static int __init prom_setprop(phandle node, const char *nodename,
>> }
>>
>> /* We can't use the standard versions because of relocation headaches. */
>> -#define isxdigit(c) (('0' <= (c) && (c) <= '9') \
>> - || ('a' <= (c) && (c) <= 'f') \
>> - || ('A' <= (c) && (c) <= 'F'))
>> +#define prom_isxdigit(c) (('0' <= (c) && (c) <= '9') \
>> + || ('a' <= (c) && (c) <= 'f') \
>> + || ('A' <= (c) && (c) <= 'F'))
>>
>> -#define isdigit(c) ('0' <= (c) && (c) <= '9')
>> -#define islower(c) ('a' <= (c) && (c) <= 'z')
>> -#define toupper(c) (islower(c) ? ((c) - 'a' + 'A') : (c))
>> +#define prom_isdigit(c) ('0' <= (c) && (c) <= '9')
>> +#define prom_islower(c) ('a' <= (c) && (c) <= 'z')
>> +#define prom_toupper(c) (prom_islower(c) ? ((c) - 'a' + 'A') : (c))
>>
>> static unsigned long prom_strtoul(const char *cp, const char **endp)
>> {
>> @@ -716,14 +716,14 @@ static unsigned long prom_strtoul(const char *cp, const char **endp)
>> if (*cp == '0') {
>> base = 8;
>> cp++;
>> - if (toupper(*cp) == 'X') {
>> + if (prom_toupper(*cp) == 'X') {
>> cp++;
>> base = 16;
>> }
>> }
>>
>> - while (isxdigit(*cp) &&
>> - (value = isdigit(*cp) ? *cp - '0' : toupper(*cp) - 'A' + 10) < base) {
>> + while (prom_isxdigit(*cp) &&
>> + (value = prom_isdigit(*cp) ? *cp - '0' : prom_toupper(*cp) - 'A' + 10) < base) {
>> result = result * base + value;
>> cp++;
>> }
>> --
>> 2.30.2
>>
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2021-06-09 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 14:49 [PATCH v1 1/1] powerpc/prom_init: Move custom isspace() to its own namespace Andy Shevchenko
2021-06-07 17:12 ` Andy Shevchenko
2021-06-09 7:00 ` Michael Ellerman [this message]
2021-06-18 3:51 ` Michael Ellerman
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=87o8cfed4v.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=paulus@samba.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