linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Paul Moore <paul@paul-moore.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Boot regression caused by kauditd
Date: Fri, 28 Apr 2017 09:11:15 -0700	[thread overview]
Message-ID: <CAM_iQpWAZPaTr_ZEqg5+Q+GUqDJSmWYjH2+8uunNwyPNAy-OSA@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhRuKG9+M6MY=KqzVvXc6P6ZPNSLwVPgWYQq23P5fT8uRg@mail.gmail.com>

On Fri, Apr 28, 2017 at 8:30 AM, Paul Moore <paul@paul-moore.com> wrote:
> On Thu, Apr 27, 2017 at 8:47 PM, Paul Moore <paul@paul-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...

  reply	other threads:[~2017-04-28 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 20:48 Boot regression caused by kauditd Cong Wang
2017-04-26 21:20 ` Paul Moore
2017-04-27  5:04   ` Cong Wang
2017-04-27 20:31   ` Cong Wang
2017-04-27 21:35     ` Cong Wang
2017-04-27 21:45       ` Cong Wang
2017-04-27 22:38         ` Paul Moore
2017-04-27 23:41           ` Cong Wang
2017-04-28  0:47             ` Paul Moore
2017-04-28 15:30               ` Paul Moore
2017-04-28 16:11                 ` Cong Wang [this message]
2017-04-28 16:26                   ` Paul Moore
2017-05-02  5:50                     ` Cong Wang

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=CAM_iQpWAZPaTr_ZEqg5+Q+GUqDJSmWYjH2+8uunNwyPNAy-OSA@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.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).