From: Greg KH <greg@kroah.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Richard W.M. Jones" <rjones@redhat.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, akpm@linux-foundation.org,
luto@kernel.org, viro@zeniv.linux.org.uk,
mathieu.desnoyers@efficios.com, zab@redhat.com,
emunson@akamai.com, paulmck@linux.vnet.ibm.com,
aarcange@redhat.com, josh@joshtriplett.org, xemul@parallels.com,
sfr@canb.auug.org.au, milosz@adfin.com, arnd@arndb.de,
ebiederm@xmission.com, gorcunov@openvz.org,
iulia.manda21@gmail.com, dave.hansen@linux.intel.com,
mguzik@redhat.com, adobriyan@gmail.com, dave@stgolabs.net,
linux-api@vger.kernel.org, gorcunov@gmail.com, fw@deneb.enyo.de
Subject: Re: [PATCH v2 0/2] vfs: Define new syscall getumask.
Date: Thu, 14 Apr 2016 12:26:16 -0700 [thread overview]
Message-ID: <20160414192616.GE20512@kroah.com> (raw)
In-Reply-To: <20160413234703.615f3016@grimm.local.home>
On Wed, Apr 13, 2016 at 11:47:03PM -0400, Steven Rostedt wrote:
> On Wed, 13 Apr 2016 06:59:50 -0700
> Greg KH <greg@kroah.com> wrote:
>
>
> > Why not add this to the ktest infrastructure, we strongly encourage that
> > for new syscalls, along with a man page patch.
>
> Do you mean the "selftest infrastructure"? As I don't see how this
> could be used with ktest.
>
> See tools/testing/selftests/
Sorry, yes, I meant selftest, not ktest, sorry for the confusion.
greg k-h
next prev parent reply other threads:[~2016-04-14 19:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 12:57 [PATCH v2 0/2] vfs: Define new syscall getumask Richard W.M. Jones
2016-04-13 12:57 ` [PATCH v2 1/2] " Richard W.M. Jones
2016-04-13 13:20 ` Cyrill Gorcunov
2016-04-13 13:57 ` Richard W.M. Jones
2016-04-13 14:02 ` Christoph Hellwig
2016-04-13 15:27 ` Mathieu Desnoyers
2016-04-13 12:57 ` [PATCH v2 2/2] x86: Wire up new getumask system call on x86 Richard W.M. Jones
2016-04-13 13:59 ` [PATCH v2 0/2] vfs: Define new syscall getumask Greg KH
2016-04-14 3:47 ` Steven Rostedt
2016-04-14 19:26 ` Greg KH [this message]
2016-04-13 15:39 ` Mathieu Desnoyers
2016-04-13 21:01 ` Mathieu Desnoyers
2016-04-14 2:13 ` Theodore Ts'o
2016-04-18 0:38 ` H. Peter Anvin
2016-04-18 1:09 ` Greg KH
2016-04-18 2:02 ` H. Peter Anvin
2016-04-18 2:12 ` Josh Triplett
2016-04-18 2:15 ` H. Peter Anvin
2016-04-18 2:37 ` Josh Triplett
2016-04-18 3:00 ` H. Peter Anvin
2016-04-18 11:39 ` Theodore Ts'o
2016-04-14 17:56 ` Andy Lutomirski
2016-04-13 15:41 ` Colin Walters
2016-04-13 16:03 ` Richard W.M. Jones
2016-04-18 1:42 ` H. Peter Anvin
2016-04-18 1:57 ` Josh Triplett
2016-04-18 9:14 ` Richard W.M. Jones
2016-04-18 10:04 ` H. Peter Anvin
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=20160414192616.GE20512@kroah.com \
--to=greg@kroah.com \
--cc=aarcange@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=ebiederm@xmission.com \
--cc=emunson@akamai.com \
--cc=fw@deneb.enyo.de \
--cc=gorcunov@gmail.com \
--cc=gorcunov@openvz.org \
--cc=hpa@zytor.com \
--cc=iulia.manda21@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mguzik@redhat.com \
--cc=milosz@adfin.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rjones@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.com \
--cc=zab@redhat.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