From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754933AbcEZUKP (ORCPT <rfc822;w@1wt.eu>);
	Thu, 26 May 2016 16:10:15 -0400
Received: from zeniv.linux.org.uk ([195.92.253.2]:44398 "EHLO
	ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753268AbcEZUKO (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 26 May 2016 16:10:14 -0400
Date: Thu, 26 May 2016 21:10:11 +0100
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sage Weil <sweil@redhat.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: [GIT PULL] Ceph updates for 4.7-rc1
Message-ID: <20160526201011.GM14480@ZenIV.linux.org.uk>
References: <alpine.DEB.2.11.1605261035390.6221@cpach.fuggernut.com>
 <CA+55aFz=U2rdLDOm=wHmS2UkmFqtx+PB--7K7B8uJtBza3dP4A@mail.gmail.com>
 <alpine.DEB.2.11.1605261446230.6221@cpach.fuggernut.com>
 <CA+55aFygBAq19UXECwQf_crUqNH4btTDircZJ=CctAHtFhnexw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+55aFygBAq19UXECwQf_crUqNH4btTDircZJ=CctAHtFhnexw@mail.gmail.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, May 26, 2016 at 12:54:27PM -0700, Linus Torvalds wrote:

> Having entirely new pull requests show up that haven't even been on my
> radar because they weren't in linux-next is annoying.

How about the things like followups to earlier merges?  I've got in
#for-linus
    update D/f/directory-locking
    add down_write_killable_nested()
    restore killability of old mutex_lock_killable(&inode->i_mutex) users

The first one probably should've been in the work.lookups merge, but
the last two clearly depend upon down_write_killable() having been already
merged...