From: Christoph Hellwig <hch@lst.de>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "Markus Elfring" <Markus.Elfring@web.de>,
"Namjae Jeon" <namjae.jeon@samsung.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
"Christoph Hellwig" <hch@lst.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sungjong Seo" <sj1557.seo@samsung.com>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
linkinjeon@gmail.com
Subject: Re: [v8 08/13] exfat: add exfat cache
Date: Wed, 8 Jan 2020 19:46:16 +0100 [thread overview]
Message-ID: <20200108184616.GA15429@lst.de> (raw)
In-Reply-To: <20200108180819.3gt6ihm4w2haustn@pali>
On Wed, Jan 08, 2020 at 07:08:19PM +0100, Pali Rohár wrote:
> On Thursday 02 January 2020 11:19:26 Markus Elfring wrote:
> > > I am planning to change to share stuff included cache with fat after
> > > exfat upstream.
> >
> > Can unwanted code duplication be avoided before?
>
> +1 Could it be possible?
Let's defer that until we have the code upstream. Getting rid
of the staging version and having proper upstream exfat support
should be a priority for now, especially as sharing will involve
coordination with multiple maintainers. If it works out nicely
I'm all for it, though!
next prev parent reply other threads:[~2020-01-08 18:46 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191220062731epcas1p475b8da9288b08c87e474a0c4e88ce219@epcas1p4.samsung.com>
2019-12-20 6:24 ` [PATCH v8 00/13] add the latest exfat driver Namjae Jeon
2019-12-20 6:24 ` [PATCH v8 01/13] exfat: add in-memory and on-disk structures and headers Namjae Jeon
2019-12-29 14:11 ` Pali Rohár
2019-12-31 13:46 ` Namjae Jeon
2020-01-02 11:06 ` Pali Rohár
2020-01-02 11:11 ` Namjae Jeon
2019-12-31 13:25 ` Markus Elfring
2019-12-31 14:05 ` Markus Elfring
2019-12-20 6:24 ` [PATCH v8 02/13] exfat: add super block operations Namjae Jeon
2019-12-29 13:40 ` Pali Rohár
2020-01-02 6:06 ` Namjae Jeon
2020-01-02 8:30 ` Pali Rohár
2020-01-02 13:13 ` Namjae Jeon
2020-01-02 13:16 ` Pali Rohár
2020-01-02 13:41 ` Namjae Jeon
2020-01-02 14:13 ` Pali Rohár
2019-12-29 13:55 ` Pali Rohár
2019-12-31 13:32 ` Namjae Jeon
2020-01-08 19:55 ` Arnd Bergmann
2020-01-09 23:36 ` Namjae Jeon
2019-12-20 6:24 ` [PATCH v8 03/13] exfat: add inode operations Namjae Jeon
2019-12-29 14:15 ` Pali Rohár
2019-12-31 13:53 ` Namjae Jeon
2019-12-20 6:24 ` [PATCH v8 04/13] exfat: add directory operations Namjae Jeon
2019-12-20 6:24 ` [PATCH v8 05/13] exfat: add file operations Namjae Jeon
2019-12-20 6:24 ` [PATCH v8 06/13] exfat: add exfat entry operations Namjae Jeon
2019-12-20 6:24 ` [PATCH v8 07/13] exfat: add bitmap operations Namjae Jeon
2019-12-20 6:24 ` [PATCH v8 08/13] exfat: add exfat cache Namjae Jeon
2019-12-29 14:23 ` Pali Rohár
2019-12-31 13:52 ` Namjae Jeon
2020-01-02 10:19 ` [v8 " Markus Elfring
2020-01-08 18:08 ` Pali Rohár
2020-01-08 18:46 ` Christoph Hellwig [this message]
2020-01-08 19:01 ` Pali Rohár
2019-12-20 6:24 ` [PATCH v8 09/13] exfat: add misc operations Namjae Jeon
2019-12-29 14:00 ` Pali Rohár
2019-12-31 13:34 ` Namjae Jeon
2019-12-20 6:24 ` [PATCH v8 10/13] exfat: add nls operations Namjae Jeon
2019-12-31 14:23 ` Markus Elfring
2019-12-31 18:01 ` Joe Perches
2020-01-02 9:56 ` Markus Elfring
2019-12-20 6:24 ` [PATCH v8 11/13] exfat: add Kconfig and Makefile Namjae Jeon
2019-12-20 6:24 ` [PATCH v8 12/13] exfat: add exfat in fs/Kconfig and fs/Makefile Namjae Jeon
2019-12-23 22:17 ` kbuild test robot
2019-12-20 6:24 ` [PATCH v8 13/13] MAINTAINERS: add exfat filesystem Namjae Jeon
2019-12-31 13:00 ` [PATCH v8 00/13] add the latest exfat driver Markus Elfring
2019-12-31 15:14 ` Matthew Wilcox
2019-12-31 23:56 ` Namjae Jeon
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=20200108184616.GA15429@lst.de \
--to=hch@lst.de \
--cc=Markus.Elfring@web.de \
--cc=gregkh@linuxfoundation.org \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=pali.rohar@gmail.com \
--cc=sj1557.seo@samsung.com \
--cc=valdis.kletnieks@vt.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