From: Jan Kara <jack@suse.cz>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org, linux-scsi <linux-scsi@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM TOPIC] Patch Submission process and Handling Internal Conflict
Date: Thu, 25 Jan 2018 11:28:29 +0100 [thread overview]
Message-ID: <20180125102829.wr4xsps5gudpreac@quack2.suse.cz> (raw)
In-Reply-To: <1516820744.3073.30.camel@HansenPartnership.com>
On Wed 24-01-18 11:05:44, James Bottomley wrote:
> I've got two community style topics, which should probably be discussed
> in the plenary
>
> 1. Patch Submission Process
>
> Today we don't have a uniform patch submission process across Storage,
> Filesystems and MM. The question is should we (or at least should we
> adhere to some minimal standards). The standard we've been trying to
> hold to in SCSI is one review per accepted non-trivial patch. For us,
> it's useful because it encourages driver writers to review each other's
> patches rather than just posting and then complaining their patch
> hasn't gone in. I can certainly think of a couple of bugs I've had to
> chase in mm where the underlying patches would have benefited from
> review, so I'd like to discuss making the one review per non-trival
> patch our base minimum standard across the whole of LSF/MM; it would
> certainly serve to improve our Reviewed-by statistics.
Well, stuff like fs/reiserfs, fs/udf, fs/isofs, or fs/quota are also parts
of filesystem space but good luck with finding reviewers for those. 99% of
patches I sent in last 10 years were just met with silence (usually there's
0-1 developer interested in that code) so I just push them to have the bug
fixed... I don't feel that as a big problem since the code is reasonably
simple, can be tested, change rate is very low. I just wanted to give that
as an example that above rule does not work for everybody.
For larger filesystems I agree 'at least one reviewer' is a good rule. XFS
is known for this, I believe btrfs pretty much enforces it as well, Ted is
not enforcing this rule for ext4 AFAIK and often it is up to him to review
patches but larger / more complex stuff generally does get reviewed. So
IMO ext4 could use some improvement but I'll leave up to Ted to decide
what's better for ext4.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-25 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 19:05 James Bottomley
2018-01-24 19:20 ` Mike Kravetz
2018-01-24 21:36 ` James Bottomley
2018-01-24 23:43 ` Darrick J. Wong
2018-01-31 16:21 ` Eric Sandeen
2018-01-24 19:26 ` Bart Van Assche
2018-01-24 21:45 ` James Bottomley
2018-01-25 10:02 ` Jan Kara
2018-01-25 10:28 ` Jan Kara [this message]
2018-01-26 12:13 ` Goldwyn Rodrigues
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=20180125102829.wr4xsps5gudpreac@quack2.suse.cz \
--to=jack@suse.cz \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox