From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [PATCH 0/5] locks: move most locks_release_private calls outside of i_lock Date: Wed, 13 Aug 2014 11:51:31 -0400 Message-ID: <20140813155131.GA5169@fieldses.org> References: <1407854893-2698-1-git-send-email-jlayton@primarydata.com> <20140813082827.1097c3ad@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jeff Layton , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org To: Stephen Rothwell Return-path: Content-Disposition: inline In-Reply-To: <20140813082827.1097c3ad@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Aug 13, 2014 at 08:28:27AM +1000, Stephen Rothwell wrote: > This s reinforced by the lack of Acked-by, Reviewed-by and Tested-by > tags ... (the addition of which would presumably require the rebase > (or rewrite) of a published git tree.) By the way, I reshuffled my branches recently so the one you pull has incoming patches that I think are mature enough to be worth testing but haven't finished review yet. That was partly Jeff's request, as he wanted his patches to get some exposure while waiting for review. It also means I can fold in some minor fixes instead of piling up fixes for nits found by the kbuild robot. (But maybe that unfairly denies it some credit, I don't know.) Anyway that means that branch is getting rewritten, say, weekly, as opposed to never (or maybe for once-in-a-year level screwups). Am I doing it wrong? --b.