All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org,
	sgrubb@redhat.com, eparis@redhat.com, peter@hda3.com
Subject: Re: [PATCH V10] fixup: audit: implement audit by executable
Date: Wed, 12 Aug 2015 22:30:39 -0400	[thread overview]
Message-ID: <4869121.dlkq9l8HZc@sifl> (raw)
In-Reply-To: <20150812151944.GC25337@madcap2.tricolour.ca>

On Wednesday, August 12, 2015 11:19:44 AM Richard Guy Briggs wrote:
> On 15/08/12, Paul Moore wrote:
> > On Wednesday, August 12, 2015 05:48:48 AM Richard Guy Briggs wrote:
> > > Do you plan to push this fix to next?
> > 
> > Patience.  Yes, I'll be pushing this to next sometime this week; as usual
> > I'll send mail when I do.
> 
> Ok, no problem, I'm not rushing.  I was unsure what your intentions were
> or whether there was more to do to help it happen.

It's merged.  I still don't know why I'm seeing that error, but the patch is 
obviously correct so I'm just going to merge it anyway and chalk it up to some 
compiler/sparse oddity.

As far as patch follow-ups, if you haven't heard back from me after four days 
or so (yes, that is as arbitrary as it sounds), it isn't a bad idea to send a 
follow-up, especially if it is a critical patch, to make sure I've seen the 
patch (things do occasionally fall through the cracks).  However, if it is 
only been a day or two and I haven't responded, rest assured I've likely seen 
your patch I'm just dealing with something else at the moment and haven't had 
the time to review/comment/merge your patch.

-- 
paul moore
security @ redhat

      reply	other threads:[~2015-08-13  2:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-08 14:20 [PATCH V10] fixup: audit: implement audit by executable Richard Guy Briggs
2015-08-08 14:20 ` Richard Guy Briggs
2015-08-10 16:22 ` Paul Moore
2015-08-10 17:29   ` Richard Guy Briggs
2015-08-10 18:43     ` Paul Moore
2015-08-11  4:15       ` Richard Guy Briggs
2015-08-12  9:48         ` Richard Guy Briggs
2015-08-12 14:21           ` Paul Moore
2015-08-12 15:19             ` Richard Guy Briggs
2015-08-13  2:30               ` Paul Moore [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=4869121.dlkq9l8HZc@sifl \
    --to=pmoore@redhat.com \
    --cc=eparis@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@hda3.com \
    --cc=rgb@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.