From: Christoph Hellwig <hch@lst.de>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2] hfsplus: avoid crash on failed block map free
Date: Wed, 19 Dec 2012 15:09:03 +0100 [thread overview]
Message-ID: <20121219140903.GA32544@lst.de> (raw)
In-Reply-To: <1355899368.2528.25.camel@slavad-ubuntu>
On Wed, Dec 19, 2012 at 10:42:48AM +0400, Vyacheslav Dubeyko wrote:
> > Yes, they've all been in linux-next for a while.
> >
> > To be more specific: is Christoph OK with a mainline merge?
>
> I think that we need to ask his about it. :-) I haven't any private
> e-mailing with him about it.
>
> Maybe, it makes sense to merge in mainline reworked error processing
> patches previously and, then, to merge the xattr support after ACLs
> support implementation.
>
> Christoph, could you share your opinion?
I haven't actually managed to look at your new xattr patches, but at
least conceptually I'm fine with them.
Let's get the error handling and misc hfsplus patches in ASAP, in the meantime
I'll get a review for the xattr bits in, and then we can decide to merge
them directly or together with the ACL bits.
next prev parent reply other threads:[~2012-12-19 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 9:31 [PATCH v2] hfsplus: avoid crash on failed block map free Vyacheslav Dubeyko
2012-11-13 22:34 ` Andrew Morton
2012-11-14 11:24 ` Christoph Hellwig
2012-11-15 7:07 ` Vyacheslav Dubeyko
2012-11-15 9:17 ` Christoph Hellwig
2012-11-15 9:31 ` Vyacheslav Dubeyko
2012-11-14 12:50 ` Vyacheslav Dubeyko
2012-12-18 22:47 ` Andrew Morton
2012-12-19 6:26 ` Vyacheslav Dubeyko
2012-12-19 6:29 ` Andrew Morton
2012-12-19 6:42 ` Vyacheslav Dubeyko
2012-12-19 14:09 ` Christoph Hellwig [this message]
2012-12-19 14:15 ` Vyacheslav Dubeyko
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=20121219140903.GA32544@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.com \
/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).