From: Christoph Hellwig <hch@infradead.org>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
Al Viro <viro@zeniv.linux.org.uk>,
Sougata Santra <sougata@tuxera.com>,
Christoph Hellwig <hch@infradead.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org Mailing List"
<linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
Szabolcs Szakacsits <szaka@tuxera.com>
Subject: Re: [PATCH] hfsplus: Remove hfsplus_file_lookup
Date: Thu, 12 Dec 2013 00:18:45 -0800 [thread overview]
Message-ID: <20131212081845.GB6754@infradead.org> (raw)
In-Reply-To: <1386830101.3972.27.camel@slavad-ubuntu>
On Thu, Dec 12, 2013 at 10:35:01AM +0400, Vyacheslav Dubeyko wrote:
> I think that I can implement support of resource forks by means of xattr
> way. Also, currently, I am implementing HFS+ compressed files support.
> So, I can clean up old-fashioned way of resource forks support in HFS+
> driver because of necessity to rework it anyway. The suggested patch
> doesn't make all necessary cleanup, from my viewpoint.
>
> Any comments?
The patch is required band aid to fix easily user visible and
triggerable breakage. As such it should go in ASAP and not be blocked
by additional cleanups. That doesn't mean that I wouldn't love to see
your planned rework and additional cleanups later.
next prev parent reply other threads:[~2013-12-12 8:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 16:56 [PATCH] hfsplus: Remove hfsplus_file_lookup Sougata Santra
2013-12-11 16:56 ` Sougata Santra
2013-12-11 19:49 ` Vyacheslav Dubeyko
2013-12-11 19:49 ` Vyacheslav Dubeyko
2013-12-11 19:11 ` Al Viro
2013-12-11 21:08 ` Anton Altaparmakov
2013-12-11 21:08 ` Anton Altaparmakov
2013-12-12 6:35 ` Vyacheslav Dubeyko
2013-12-12 6:35 ` Vyacheslav Dubeyko
2013-12-12 8:18 ` Christoph Hellwig [this message]
2013-12-12 8:18 ` Christoph Hellwig
2013-12-12 8:16 ` Christoph Hellwig
2013-12-12 17:02 Sougata Santra
2013-12-12 17:02 ` Sougata Santra
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=20131212081845.GB6754@infradead.org \
--to=hch@infradead.org \
--cc=aia21@cam.ac.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=sougata@tuxera.com \
--cc=szaka@tuxera.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.