[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpWAZPaTr_ZEqg5+Q+GUqDJSmWYjH2+8uunNwyPNAy-OSA@mail.gmail.com>
Date: Fri, 28 Apr 2017 09:11:15 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Paul Moore <paul@...l-moore.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: Boot regression caused by kauditd
On Fri, Apr 28, 2017 at 8:30 AM, Paul Moore <paul@...l-moore.com> wrote:
> On Thu, Apr 27, 2017 at 8:47 PM, Paul Moore <paul@...l-moore.com> wrote:
>> In that case please send a proper inline patch to the audit mailing list
>> and we'll review it.
>>
>> Thanks.
>
> Now that I'm back in front of a proper screen/keyboard I've been
> looking over your patch and while you are very right in that the
> current RCU usage is very wrong, there are quite a few things I would
> like to see changed in your patch ... I'm working on something right
> now, I'll post an RFC draft to the audit list and CC you once I get
> this sorted out, expect something in a few hours.
>
> Also, once you've had a look at this new patch, and assuming you are
> okay with it, I'd like to add your sign-off to it. This may not be
> your patch exactly, but a significant portion of it is borrowed from
> your patch yesterday.
So your review process is: if people's V1 patch is not perfect, you
will rewrite it by yourself?
But the normal review process is: people need to address feedback
and send V2, V3 etc..
That's too odd. Someday, no one will be willing to work on audit
patches except yourself.
No offense, just don't feel your review process is cooperative...
Powered by blists - more mailing lists