From: David Miller <davem@davemloft.net>
To: sgrubb@redhat.com
Cc: netdev@vger.kernel.org, linux-audit@redhat.com, selinux@tycho.nsa.gov
Subject: Re: [PATCH 1/1] NetLabel: audit fixups due to delayed feedback
Date: Fri, 29 Sep 2006 17:05:43 -0700 (PDT) [thread overview]
Message-ID: <20060929.170543.90121035.davem@davemloft.net> (raw)
In-Reply-To: <200609292000.42544.sgrubb@redhat.com>
From: Steve Grubb <sgrubb@redhat.com>
Date: Fri, 29 Sep 2006 20:00:42 -0400
> On Friday 29 September 2006 18:39, paul.moore@hp.com wrote:
> > This should make NetLabel more consistent with other kernel
> > generated audit messages specifying configuration changes.
>
> OK, this looks better. We may fine tune the messages later after we try it
> out, but all the issues I saw are fixed. ACK.
Patch applied.
prev parent reply other threads:[~2006-09-30 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 22:39 [PATCH 0/1] NetLabel audit fixup paul.moore
2006-09-29 22:39 ` [PATCH 1/1] NetLabel: audit fixups due to delayed feedback paul.moore
2006-09-30 0:00 ` Steve Grubb
2006-09-30 0:05 ` David Miller [this message]
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=20060929.170543.90121035.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-audit@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
--cc=sgrubb@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;
as well as URLs for NNTP newsgroup(s).