From: Greg KH <gregkh@linuxfoundation.org>
To: Ju Hyung Park <qkrwngud825@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, linkinjeon@gmail.com,
Valdis Kletnieks <valdis.kletnieks@vt.edu>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Namjae Jeon <namjae.jeon@samsung.com>,
linux-kernel@vger.kernel.org, alexander.levin@microsoft.com,
sergey.senozhatsky@gmail.com, linux-fsdevel@vger.kernel.org,
sj1557.seo@samsung.com
Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to
Date: Wed, 18 Sep 2019 13:05:48 +0200 [thread overview]
Message-ID: <20190918110548.GA1894362@kroah.com> (raw)
In-Reply-To: <CAD14+f1yT2_d8RP2a2NqAVYAkmB4ti6KjSsV2sM8SVCOQ_M=RQ@mail.gmail.com>
On Wed, Sep 18, 2019 at 07:46:25PM +0900, Ju Hyung Park wrote:
> On Wed, Sep 18, 2019 at 7:09 PM Dan Carpenter <dan.carpenter@oracle.com> wrote:
> > Use Kconfig.
>
> Not just that.
> There are a lot of non-static functions that's not marked ex/sdfat-specific.
> (which we would have to clean it up eventually)
Then clean them up :)
> Even with sdFAT base, there are some non-static functions named as exfat.
Then just force both filesystems to only be built as a module and all
should be fine, right?
> Figuring out a solution for this is pretty pointless imho when one of
> the drivers will be dropped soon(ish) anyways.
Given we only have one filesytem that is submitted in patch form, I
think people are making a lot of noise over nothing :)
thanks,
greg k-h
next prev parent reply other threads:[~2019-09-18 11:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190917025738epcas1p1f1dd21ca50df2392b0f84f0340d82bcd@epcas1p1.samsung.com>
[not found] ` <003601d56d03$aa04fa00$fe0eee00$@samsung.com>
2019-09-17 3:02 ` [PATCH] staging: exfat: add exfat filesystem code to Namjae Jeon
2019-09-17 4:19 ` Valdis Klētnieks
2019-09-17 5:31 ` Park Ju Hyung
2019-09-17 5:47 ` Greg KH
2019-09-17 6:04 ` Ju Hyung Park
2019-09-18 2:35 ` Namjae Jeon
2019-09-18 6:16 ` 'Greg KH'
2019-09-18 6:33 ` Sergey Senozhatsky
2019-09-18 8:26 ` 'Greg KH'
2019-09-18 8:51 ` Sergey Senozhatsky
2019-09-18 9:01 ` Ju Hyung Park
2019-09-18 9:24 ` Dan Carpenter
2019-09-18 9:53 ` Ju Hyung Park
2019-09-18 10:08 ` Dan Carpenter
2019-09-18 10:46 ` Ju Hyung Park
2019-09-18 11:05 ` Greg KH [this message]
2019-09-19 2:14 ` Namjae Jeon
2019-09-30 4:25 ` Namjae Jeon
2019-09-30 6:08 ` 'Greg KH'
2019-09-17 4:56 ` 'Greg KH'
2019-09-17 5:15 ` Gao Xiang
2019-08-28 16:08 [PATCH] staging: exfat: add exfat filesystem code to staging Greg Kroah-Hartman
2019-09-14 13:39 ` [PATCH] staging: exfat: add exfat filesystem code to Park Ju Hyung
2019-09-15 13:54 ` Greg KH
2019-09-15 16:11 ` Ju Hyung Park
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=20190918110548.GA1894362@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=qkrwngud825@gmail.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@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