public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Yury Norov <ynorov@caviumnetworks.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 1/4] Add INTERNAL_SYSCALL_CALL
Date: Tue, 23 Aug 2016 19:16:00 -0000	[thread overview]
Message-ID: <72b566be-074f-9575-46fe-df8f04fcedb7@linaro.org> (raw)
In-Reply-To: <20160822152826.GE15745@yury-N73SV>

Thanks for review, comments below.

On 22/08/2016 12:28, Yury Norov wrote:
>> ---
>>  sysdeps/unix/sysdep.h | 42 +++++++++++++++++++++++++++++++++++++++---
>>  2 files changed, 56 insertions(+), 3 deletions(-)
>>
>> +
>> +#define __INTERNAL_SYSCALL_NARGS_X(a,b,c,d,e,f,g,h,n,...) n
> 
> Missed whitespaces after commas?
> 

Ack.

>> +#define __INTERNAL_SYSCALL_NARGS(...) \
>> +  __INTERNAL_SYSCALL_NARGS_X (__VA_ARGS__,7,6,5,4,3,2,1,0,)
> 
> Same
> 

Ack.

>> +#define __INTERNAL_SYSCALL_CONCAT_X(a,b)     a##b
> 
> Same
> 

Ack.

>> +#define __INTERNAL_SYSCALL_CONCAT(a,b)       __SYSCALL_CONCAT_X (a, b)
>> +#define __INTERNAL_SYSCALL_DISP(b,err,...) \
>> +  __INTERNAL_SYSCALL_CONCAT (b,__SYSCALL_NARGS(__VA_ARGS__))(err,__VA_ARGS__)
> 
> Missed whitespaces after commas and before opening braces?
> 

Ack.

>> +
>> +/* Issue a syscall defined by syscall number plus any other argument required.
>> +   It is similar to INLINE_SYSCALL macro, but without the need to pass the
> 
> Did you mean INTERNAL_SYSCALL macro?
> 

Yes, I will fix it.

>> +   expected argument number as second parameter.  */
>> +#define INTERNAL_SYSCALL_CALL(nr, err, ...) \
>> +  __INTERNAL_SYSCALL_DISP (__INTERNAL_SYSCALL, nr, err, __VA_ARGS__)
>> +
>>  #define __SYSCALL0(name) \
>>    INLINE_SYSCALL (name, 0)
>>  #define __SYSCALL1(name, a1) \
>> @@ -49,17 +80,22 @@
>>  #define __SYSCALL_DISP(b,...) \
>>    __SYSCALL_CONCAT (b,__SYSCALL_NARGS(__VA_ARGS__))(__VA_ARGS__)
>>  
>> -#define __SYSCALL_CALL(...) __SYSCALL_DISP (__SYSCALL, __VA_ARGS__)
>> +/* Issue a syscall defined by syscall number plus any other argument required.
>> +   Any error will be handled using arch defined macros and errno will be se
>> +   accordingly.
>> +   It is similar to INLINE_SYSCALL macro, but without the need to pass the
>> +   expected argument number as second parameter.  */
>> +#define INLINE_SYSCALL_CALL(...) __SYSCALL_DISP (__SYSCALL, __VA_ARGS__)
> 
> Missed whitespaces after commas and before opening braces?

For INLINE_SYSCALL_DEFINITION you mean? I do not think so, 'indent' also
shows no change for this specific snippet. 

  reply	other threads:[~2016-08-23 19:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 14:42 [PATCH 0/4] Linux fallocate, posix_fallocate, and posix_fadvise consolidation Adhemerval Zanella
2016-08-19 14:42 ` [PATCH 1/4] Add INTERNAL_SYSCALL_CALL Adhemerval Zanella
2016-08-22 15:28   ` Yury Norov
2016-08-23 19:16     ` Adhemerval Zanella [this message]
2016-08-23 19:20       ` Yury Norov
2016-08-19 14:42 ` [PATCH 2/4] Consolidate fallocate{64} implementations Adhemerval Zanella
2016-08-22 15:14   ` Yury Norov
2016-08-23 19:21     ` Adhemerval Zanella
2016-08-19 14:42 ` [PATCH 4/4] Consolidate posix_fadvise implementations Adhemerval Zanella
2016-08-22 15:08   ` Yury Norov
2016-08-23 19:29     ` Adhemerval Zanella
2016-08-23 20:00       ` Yury Norov
2016-08-24 14:29         ` Adhemerval Zanella
2016-08-24  3:53   ` Yury Norov
2016-08-24 14:40     ` Adhemerval Zanella
2016-09-25 10:42   ` Yury Norov
2016-09-26 19:44     ` Adhemerval Zanella
2016-08-19 14:42 ` [PATCH 3/4] Consolidate posix_fallocate{64} implementations Adhemerval Zanella
2016-08-22 14:35   ` Yury Norov
2016-08-23 19:22     ` Adhemerval Zanella
2016-08-22 14:31 ` [PATCH 0/4] Linux fallocate, posix_fallocate, and posix_fadvise consolidation Yury Norov
2016-09-20 15:02 [PATCH 0/4] Linux lseek and {f}truncate syscall consolidation Adhemerval Zanella
2016-09-20 15:02 ` [PATCH 1/4] Add INTERNAL_SYSCALL_CALL Adhemerval Zanella
2016-09-20 21:36   ` Florian Weimer
2016-09-21 18:00     ` Adhemerval Zanella
2016-09-21 19:22       ` Florian Weimer
2016-09-22 13:43         ` Adhemerval Zanella
2016-09-22 20:34           ` Florian Weimer
2016-09-23 14:16             ` Adhemerval Zanella
2016-09-23 20:39               ` Florian Weimer

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=72b566be-074f-9575-46fe-df8f04fcedb7@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=ynorov@caviumnetworks.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).