From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Boaz Harrosh <ooo@electrozaur.com>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [GIT PULL] Orangefs (text only resend)
Date: Fri, 11 Sep 2015 16:20:38 -0700 [thread overview]
Message-ID: <CA+55aFzkYr+UEU_oC+p2QN0N+CciWN6PYRKjDsoeOjz6eGuEXw@mail.gmail.com> (raw)
In-Reply-To: <CAOg9mSTuo8Y2XTJWx=8443Ps=mxmSP-qxdRRt80FfWXECPdWZA@mail.gmail.com>
On Fri, Sep 11, 2015 at 2:12 PM, Mike Marshall <hubcap@omnibond.com> wrote:
>
> Anyhow, what's in Linux next continues to pass all our tests, though the
> code needs improved in the ways mentioned by Al and Linus... I guess
> the merge window ends today?
Well, technically it ends Sunday, since I don't tend to distinguish
weekdays from weekends much, but I tend to frown on last-minute
submissions and I may just decide that I'm done on Saturday.
Yours isn't a last-minute submission, but I suspect that by now the
sane thing to do is to just say "4.4 material". It sounds like you
clearly aren't twiddling your thumbs, and can usefully continue
development for at least next week with just on the iovec stuff, and I
don't think this is a "must hit 4.3" thing, so there's no huge reason
to not let it slide until the next merge window.
And if you have a grudging ack by then from Al, I'll have no issues
merging it early next merge window ;)
Linus
next prev parent reply other threads:[~2015-09-11 23:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 15:42 [GIT PULL] Orangefs (text only resend) Mike Marshall
2015-09-02 23:34 ` Linus Torvalds
2015-09-03 1:13 ` Mike Marshall
2015-09-03 1:28 ` Linus Torvalds
2015-09-03 20:22 ` Linus Torvalds
2015-09-03 22:18 ` Mike Marshall
2015-09-03 22:44 ` Greg Kroah-Hartman
2015-09-06 6:35 ` Christoph Hellwig
2015-09-06 9:08 ` Al Viro
2015-09-06 14:52 ` Mike Marshall
2015-09-06 15:00 ` Mike Marshall
2015-09-06 20:20 ` Al Viro
2015-09-07 6:37 ` Al Viro
2015-09-07 21:10 ` Mike Marshall
2015-09-07 23:22 ` Al Viro
2015-09-08 0:47 ` Theodore Ts'o
2015-09-08 2:49 ` Dave Chinner
2015-09-08 14:48 ` Christoph Hellwig
2015-09-08 18:21 ` Mike Marshall
2015-09-09 15:05 ` Mike Marshall
2015-09-11 21:12 ` Mike Marshall
2015-09-11 22:24 ` Al Viro
2015-09-13 11:56 ` Mike Marshall
2015-09-11 23:20 ` Linus Torvalds [this message]
2015-09-13 11:59 ` Mike Marshall
2015-09-06 14:35 ` Mike Marshall
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=CA+55aFzkYr+UEU_oC+p2QN0N+CciWN6PYRKjDsoeOjz6eGuEXw@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ooo@electrozaur.com \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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).