From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mike Marshall <hubcap@omnibond.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Martin Brandenburg <martin@omnibond.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Orangefs, v4.5 and the merge window...
Date: Sat, 26 Mar 2016 00:21:17 +0000 [thread overview]
Message-ID: <20160326002116.GK17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAOg9mSSqcCfwCC5BVezQJ6CH+yeSXvHA9Nia+FXPuhUPm7cF8Q@mail.gmail.com>
On Mon, Mar 14, 2016 at 05:03:55PM -0400, Mike Marshall wrote:
> Hi Al (and everyone)...
>
> git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git
> for-next
>
> ... is updated to v4.5, it has the follow_link -> get_link change.
>
> I worked today to clean up the debugfs (and sysfs) problems,
> and we'll keep ticking things off the list, perhaps I should be
> posting patches here for review instead automatically updating
> for-next when we work on an issue...
>
> We're working on putting "the list" in a place that can be
> viewed by everyone and edited by both Martin and myself...
FWIW, I've ported several cleanups + short read/write on error + lseek
fixes + orangefs_superblocks locking fixes on top of that branch and pushed
into vfs.git#orangefs-untested.
I think it can be merged this cycle; if the fixes above really work, this
+ Martin's latest should leave only the handling of allocation failures in
debugfs-related code.
Linus, would you be OK with that thing going into -rc2? It's self-contained
and I think it's in reasonably sane shape. If not for the last locking fixes,
I would even suggest -rc1 with fixups of debugfs issues during the next week,
but that last commit got no testing whatsoever... ;-/
I would prefer if pull request went from Mike, once he's OK with the whole
set, but as far as I'm concerned the material in his #for-next + my pile above
+ Martin's branch (getattr fixes) should be OK for mainline merge.
next prev parent reply other threads:[~2016-03-26 0:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 20:18 Orangefs, v4.5 and the merge window Mike Marshall
2016-03-11 21:47 ` Al Viro
2016-03-11 22:35 ` Mike Marshall
2016-03-14 21:03 ` Mike Marshall
2016-03-26 0:21 ` Al Viro [this message]
2016-03-26 1:00 ` Mike Marshall
[not found] ` <CA+55aFzLC_pdj_ds82YYab5D7jpYMj26s0Frofxxhk=j7SqnjA@mail.gmail.com>
2016-03-26 1:01 ` Al Viro
2016-03-26 1:07 ` Mike Marshall
[not found] ` <CA+55aFysWS9mP+QgfAR6LZpEbkp61MUPQu0zDoq7cafmr3M8SA@mail.gmail.com>
2016-03-26 3:55 ` Mike Marshall
2016-03-26 4:30 ` Al Viro
2016-03-26 12:07 ` Mike Marshall
2016-03-26 14:47 ` Al Viro
2016-03-26 15:34 ` Mike Marshall
2016-03-26 15:50 ` Al Viro
2016-03-26 17:36 ` Mike Marshall
2016-03-26 18:28 ` Al Viro
2016-03-26 18:37 ` Al Viro
2016-03-26 19:00 ` Mike Marshall
2016-03-26 19:51 ` Linus Torvalds
2016-03-26 20:47 ` Mike Marshall
2016-03-26 21:00 ` Linus Torvalds
2016-03-26 1:02 ` Mike Marshall
2016-03-15 4:04 ` Martin Brandenburg
2016-03-15 16:45 ` Martin Brandenburg
2016-03-17 20:45 ` [PATCH] orangefs: getattr work (was: Re: Orangefs, v4.5 and the merge window...) Martin Brandenburg
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=20160326002116.GK17997@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin@omnibond.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).