From: Eric Paris <eparis@redhat.com>
To: linux-audit@redhat.com
Subject: Do we need entry,always rules?
Date: Tue, 08 Nov 2011 16:38:20 -0500 [thread overview]
Message-ID: <1320788300.10093.42.camel@localhost> (raw)
The kernel will take them, but I believe we decided to deprecate them.
I can remove some 'dead' code from the kernel and just return -EINVAL if
someone tries to set one. Anyone see a problem with that?
-Eric
next reply other threads:[~2011-11-08 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 21:38 Eric Paris [this message]
2011-11-08 22:18 ` Do we need entry,always rules? Steve Grubb
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=1320788300.10093.42.camel@localhost \
--to=eparis@redhat.com \
--cc=linux-audit@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