All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/userfaultfd01: Always require CAP_SYS_PTRACE
Date: Wed, 22 Jan 2020 09:04:57 +0800	[thread overview]
Message-ID: <5E279FB9.6010108@cn.fujitsu.com> (raw)
In-Reply-To: <20200121101513.GA9254@gacrux.arch.suse.de>

On 2020/1/21 18:17, Petr Vorel wrote:
> Hi Xu,
>
>> We have pushed "syscalls/userfaultfd01: add hint about unprivileged_userfaultfd" patch(v2)[1].
>> This is v1.  li Wang and me both think adding hint is more wise, more info see[2].
>> [1] https://github.com/linux-test-project/ltp/commit/7dc571d3ad1908d6e50163a06ef848f096fe880a
>> [2] http://lists.linux.it/pipermail/ltp/2020-January/014921.html
> Thanks for notification, I'll check previous commits next time!
>
> BTW this was caused by maintainers not updating patchwork :(.
> Would you mind to register to patchwork and check state of your tickets time to
> time [1]. You'd be able to change state of your own patches.
Hi Petr,

Thanks for your effort.
Xu is my colleague and I helped him change the state to superseded. :-)

Best Regards,
Xiao Yang
> Kind regards,
> Petr
>
> [1] https://patchwork.ozlabs.org/project/ltp/list/?submitter=76329
>




  reply	other threads:[~2020-01-22  1:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05  7:55 [LTP] [PATCH] syscalls/userfaultfd01: Always require CAP_SYS_PTRACE Yang Xu
2020-01-21  5:24 ` Petr Vorel
2020-01-21  5:54   ` Yang Xu
2020-01-21 10:17     ` Petr Vorel
2020-01-22  1:04       ` Xiao Yang [this message]
2020-01-22  4:01         ` Yang Xu
2020-01-22  7:42           ` Petr Vorel

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=5E279FB9.6010108@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.