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
Date: Thu, 26 May 2016 21:10:11 +0100 [thread overview]
Message-ID: <20160526201011.GM14480@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFygBAq19UXECwQf_crUqNH4btTDircZJ=CctAHtFhnexw@mail.gmail.com>
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...
next prev parent reply other threads:[~2016-05-26 20:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 18:18 [GIT PULL] Ceph updates for 4.7-rc1 Sage Weil
2016-05-26 18:31 ` Linus Torvalds
2016-05-26 19:02 ` Sage Weil
2016-05-26 19:54 ` Linus Torvalds
2016-05-26 20:10 ` Al Viro [this message]
2016-05-26 21:18 ` Linus Torvalds
2016-05-26 21:13 ` Linus Torvalds
2016-05-26 21:46 ` Sage Weil
2016-05-27 2:16 ` Linus Torvalds
2016-06-10 20:42 ` Arnd Bergmann
2016-06-10 21:32 ` Linus Torvalds
2016-06-10 23:04 ` Arnd Bergmann
2016-06-11 22:50 ` Arnd Bergmann
2016-06-13 13:06 ` Arnd Bergmann
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=20160526201011.GM14480@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sweil@redhat.com \
--cc=torvalds@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;
as well as URLs for NNTP newsgroup(s).