From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: "peter enderborg" <peter.enderborg@sony.com>,
"Thiébaud Weksteen" <tweek@google.com>,
"Paul Moore" <paul@paul-moore.com>
Cc: Nick Kralevich <nnk@google.com>,
Eric Paris <eparis@parisplace.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, selinux@vger.kernel.org
Subject: Re: [PATCH 2/2] selinux: add attributes to avc tracepoint
Date: Thu, 6 Aug 2020 08:32:38 -0400 [thread overview]
Message-ID: <971592b6-5d5f-05d8-d243-b521fe65577d@gmail.com> (raw)
In-Reply-To: <8627d780-0e19-6755-0de5-c686deb0f5de@sony.com>
On 8/6/20 8:24 AM, peter enderborg wrote:
> On 8/6/20 2:11 PM, Stephen Smalley wrote:
>> On 8/6/20 4:03 AM, Thiébaud Weksteen wrote:
>>
>>> From: Peter Enderborg <peter.enderborg@sony.com>
>>>
>>> Add further attributes to filter the trace events from AVC.
>> Please include sample usage and output in the description.
>>
>>
> Im not sure where you want it to be.
>
> In the commit message or in a Documentation/trace/events-avc.rst ?
I was just asking for it in the commit message / patch description. I
don't know what is typical for Documentation/trace.
next prev parent reply other threads:[~2020-08-06 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 8:03 [PATCH 1/2] selinux: add tracepoint on denials Thiébaud Weksteen
2020-08-06 8:03 ` [PATCH 2/2] selinux: add attributes to avc tracepoint Thiébaud Weksteen
2020-08-06 12:11 ` Stephen Smalley
2020-08-06 12:24 ` peter enderborg
2020-08-06 12:32 ` Stephen Smalley [this message]
2020-08-06 13:45 ` Stephen Smalley
2020-08-06 13:49 ` Stephen Smalley
2020-08-06 14:51 ` peter enderborg
2020-08-06 15:03 ` Stephen Smalley
2020-08-06 15:59 ` peter enderborg
2020-08-06 16:37 ` Steven Rostedt
2020-08-07 2:22 ` Paul Moore
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=971592b6-5d5f-05d8-d243-b521fe65577d@gmail.com \
--to=stephen.smalley.work@gmail.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=eparis@parisplace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mingo@redhat.com \
--cc=nnk@google.com \
--cc=paul@paul-moore.com \
--cc=peter.enderborg@sony.com \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=selinux@vger.kernel.org \
--cc=tweek@google.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