public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jason Xing <kerneljasonxing@linux.alibaba.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 2/2] lapi/syscalls: Add syscall numbers for process_vm_readv/_writev
Date: Thu, 06 Dec 2018 11:37:55 +0800	[thread overview]
Message-ID: <5C089993.1010505@linux.alibaba.com> (raw)
In-Reply-To: <20181205220747.GD21236@x230>



On 2018/12/6 上午6:07, Petr Vorel wrote:
> Hi Jason,
>
>> Signed-off-by: Jason Xing <kerneljasonxing@linux.alibaba.com>
>> Signed-off-by: Caspar Zhang <caspar@linux.alibaba.com>
>> ---
>
> ...
>> diff --git a/include/lapi/syscalls/aarch64.in b/include/lapi/syscalls/aarch64.in
>> index c7ed2fe..bf04895 100644
>> --- a/include/lapi/syscalls/aarch64.in
>> +++ b/include/lapi/syscalls/aarch64.in
>> --- a/include/lapi/syscalls/arm.in
>> +++ b/include/lapi/syscalls/arm.in
>> @@ -334,6 +334,8 @@ accept4 (__NR_SYSCALL_BASE+366)
>>   fanotify_init (__NR_SYSCALL_BASE+367)
>>   fanotify_mark (__NR_SYSCALL_BASE+368)
>>   prlimit64 (__NR_SYSCALL_BASE+369)
>> +process_vm_readv(__NR_SYSCALL_BASE+376)
>> +process_vm_writev(__NR_SYSCALL_BASE+377)
> This triggered error during generation headers:
> invalid line found: process_vm_readv(__NR_SYSCALL_BASE+376)
> (reproducible by: cd $l/include/lapi/syscalls; ./regen.sh)
>
> and thus build error:
> ../../../../include/lapi/syscalls.h:13: error: unterminated #ifndef
>   #ifndef __LAPI_SYSCALLS_H__
>
> I fixed it by adding space:
>
> -process_vm_readv(__NR_SYSCALL_BASE+376)
> -process_vm_writev(__NR_SYSCALL_BASE+377)
> +process_vm_readv (__NR_SYSCALL_BASE+376)
> +process_vm_writev (__NR_SYSCALL_BASE+377)
>
> + put this commit first and pushed.

Thanks for your instructions.

>
> Thanks for your patches.
>
> Kind regards,
> Petr
>

  reply	other threads:[~2018-12-06  3:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  9:43 [LTP] [PATCH] syscalls/cma: test case should return TCONF if syscall doesn't exist Jason Xing
2018-12-03  9:58 ` Jan Stancek
2018-12-04  2:49   ` Jason Xing
2018-12-04  8:54     ` Jan Stancek
2018-12-05 13:43       ` [LTP] [PATCH v2 1/2] " Jason Xing
2018-12-05 13:43         ` [LTP] [PATCH v2 2/2] lapi/syscalls: Add syscall numbers for process_vm_readv/_writev Jason Xing
2018-12-05 22:07           ` Petr Vorel
2018-12-06  3:37             ` Jason Xing [this message]
2019-02-15 10:50         ` [LTP] [PATCH v2 1/2] syscalls/cma: test case should return TCONF if syscall doesn't exist Li Wang
2019-02-15 13:53           ` Jan Stancek
2019-02-16  7:18             ` Li Wang
2019-02-16 10:28               ` Jan Stancek
2019-02-22 18:29                 ` Jan Stancek
2019-02-23  6:21                   ` Caspar Zhang
2019-02-25  8:22                     ` [LTP] [PATCH] syscalls/cma: fix the failure of compiling with O2 option Jason Xing
2019-02-25 10:34                       ` Li Wang
2019-02-25 10:47                       ` Jan Stancek
2019-02-25 13:16                         ` Caspar Zhang
2019-02-26  1:42                           ` [LTP] [PATCH v2] " Jason Xing
2019-02-26  2:22                             ` [LTP] [PATCH v3] " Jason Xing
2019-02-26  3:17                               ` Li Wang
2019-02-26 16:03                               ` Jan Stancek
2019-02-26  2:00                         ` [LTP] [PATCH] " Jason Xing

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=5C089993.1010505@linux.alibaba.com \
    --to=kerneljasonxing@linux.alibaba.com \
    --cc=ltp@lists.linux.it \
    /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