netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: paul.moore@hp.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 20:00:42 -0400	[thread overview]
Message-ID: <200609292000.42544.sgrubb@redhat.com> (raw)
In-Reply-To: <20060929224355.253290000@hp.com>

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.

-Steve

  reply	other threads:[~2006-09-30  0:00 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 [this message]
2006-09-30  0:05     ` David Miller

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=200609292000.42544.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul.moore@hp.com \
    --cc=selinux@tycho.nsa.gov \
    /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).