linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	tytso@mit.edu
Subject: Re: linus-next stats (Re: Linux 3.15-rc1 out, merge window closed)
Date: Thu, 17 Apr 2014 21:34:12 +0100	[thread overview]
Message-ID: <20140417203412.GB18016@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20140414180629.198f98cadef124a99439b0b1@canb.auug.org.au>

On Mon, Apr 14, 2014 at 06:06:29PM +1000, Stephen Rothwell wrote:
> Top ten authors:
> 
>      61 viro@zeniv.linux.org.uk

Guilty as charged.  Hopefully, this cycle it'll be better - I've just opened 
vfs.git#for-next branch (more iov_iter stuff, for now).  There's a couple
of trivial conflicts with ceph and cifs trees (I can send you a prefered
conflict resolution if you want, but it's really as trivial as it gets) and
one non-trivial in ext4 that I've dealt with by merging a piece of ext4
branch up to the relevant point.  As long as ext4.git#dev isn't rebased,
everything should remain fine, when/if it does I'll just redo that merge.
BTW, ext4 side of that thing is *still* not quite right - playing with
rlimit allows one to smuggle an unaligned write past that check...

      reply	other threads:[~2014-04-17 20:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 23:05 Linux 3.15-rc1 out, merge window closed Linus Torvalds
2014-04-13 23:18 ` Stephen Rothwell
2014-04-14  0:32   ` Stephen Rothwell
2014-04-14  8:06 ` linus-next stats (Re: Linux 3.15-rc1 out, merge window closed) Stephen Rothwell
2014-04-17 20:34   ` Al Viro [this message]

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=20140417203412.GB18016@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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).