All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
Subject: [PATCH v3] staging: erofs: disable compiling temporarile
Date: Tue, 7 Aug 2018 14:31:49 +0200	[thread overview]
Message-ID: <20180807123149.GC9359@kroah.com> (raw)
In-Reply-To: <309c110f-83ca-f79e-c8ff-201fe9a9f027@huawei.com>

On Tue, Aug 07, 2018@06:42:23PM +0800, Chao Yu wrote:
> I found that erofs-related patch was merged a little bit quickly, so that we may
> miss Reviewed-by tag in that merged patch due to reviewer replied to the patch late.
> 
> Out of curiosity, is there any rule for picking up and merging patches in
> staging-{test,next} tree? like merging the patch if there is at least one guy
> replies an ACK or no one object for some time?

That's what normally happens, I just was processing staging patches very
quickly for a few days and got to them before you were able to review
it.  That is not the normal state of things :)

And remember, anyone can end up merging changes to your code, being a
maintainers is not a "gatekeeper", it is a role where you are
responsible for the code, but if other "responsible" people change it,
that is also fine.

thanks,

greg k-h

  reply	other threads:[~2018-08-07 12:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 14:34 [PATCH v3] staging: erofs: disable compiling temporarile Chao Yu
2018-08-02 14:34 ` Chao Yu
2018-08-02 17:33 ` Greg KH
2018-08-02 17:33   ` Greg KH
2018-08-03  1:18   ` Gao Xiang
2018-08-03  1:18     ` Gao Xiang
2018-08-03  1:35   ` Chao Yu
2018-08-03  1:35     ` Chao Yu
2018-08-06  3:07   ` Chao Yu
2018-08-07  9:17     ` Greg KH
2018-08-07 10:42       ` Chao Yu
2018-08-07 12:31         ` Greg KH [this message]
2018-08-07 14:12           ` Gao Xiang
2018-08-07 14:23           ` Chao Yu

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=20180807123149.GC9359@kroah.com \
    --to=gregkh@linuxfoundation.org \
    /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.