From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Moore Subject: Re: [PATCH V10] fixup: audit: implement audit by executable Date: Wed, 12 Aug 2015 22:30:39 -0400 Message-ID: <4869121.dlkq9l8HZc@sifl> References: <8e78d1dca7d8ecd20d3cbdb9a008950417570866.1439036800.git.rgb@redhat.com> <55367298.NHbID3lDFH@sifl> <20150812151944.GC25337@madcap2.tricolour.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <20150812151944.GC25337@madcap2.tricolour.ca> Sender: linux-kernel-owner@vger.kernel.org To: Richard Guy Briggs Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org, sgrubb@redhat.com, eparis@redhat.com, peter@hda3.com List-Id: linux-audit@redhat.com 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