All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ju Hyung Park <qkrwngud825@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	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 18:53:49 +0900	[thread overview]
Message-ID: <CAD14+f1yQWoZH4onJwbt1kezxyoHW147HA-1p+U0dVo3r=mqBw@mail.gmail.com> (raw)
In-Reply-To: <20190918092405.GC2959@kadam>

Hi Dan,

On Wed, Sep 18, 2019 at 6:27 PM Dan Carpenter <dan.carpenter@oracle.com> wrote:
> Put it in drivers/staging/sdfat/.

It'll conflict with the current exfat staging drivers.
And moreover, I don't think it makes sense to use sdfat naming in mainline.

Samsung uses it since it handles all fat filesystems.
From what I can tell, that's not in mainline's interests:
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-next&id=58985a9d2d03e977db93bf574a16162766a318fe

What I'm proposing is to remove the current exfat drivers and add
sdfat-based one(that I removed fat16/32 handlings and renamed to
exfat).

> But really we want someone from Samsung to say that they will treat
> the staging version as upstream.

Agreed.
Perhaps Namjae didn't pick up our questions with all those mails we
sent during last few days.

Maybe ping him again?

Thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Ju Hyung Park <qkrwngud825@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: 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>,
	Greg KH <gregkh@linuxfoundation.org>,
	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 18:53:49 +0900	[thread overview]
Message-ID: <CAD14+f1yQWoZH4onJwbt1kezxyoHW147HA-1p+U0dVo3r=mqBw@mail.gmail.com> (raw)
In-Reply-To: <20190918092405.GC2959@kadam>

Hi Dan,

On Wed, Sep 18, 2019 at 6:27 PM Dan Carpenter <dan.carpenter@oracle.com> wrote:
> Put it in drivers/staging/sdfat/.

It'll conflict with the current exfat staging drivers.
And moreover, I don't think it makes sense to use sdfat naming in mainline.

Samsung uses it since it handles all fat filesystems.
From what I can tell, that's not in mainline's interests:
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-next&id=58985a9d2d03e977db93bf574a16162766a318fe

What I'm proposing is to remove the current exfat drivers and add
sdfat-based one(that I removed fat16/32 handlings and renamed to
exfat).

> But really we want someone from Samsung to say that they will treat
> the staging version as upstream.

Agreed.
Perhaps Namjae didn't pick up our questions with all those mails we
sent during last few days.

Maybe ping him again?

Thanks.
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2019-09-18  9:54 UTC|newest]

Thread overview: 48+ 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  3:02     ` Namjae Jeon
2019-09-17  4:19     ` Valdis Klētnieks
2019-09-17  4:19       ` Valdis Klētnieks
2019-09-17  5:31       ` Park Ju Hyung
2019-09-17  5:31         ` Park Ju Hyung
2019-09-17  5:47         ` Greg KH
2019-09-17  5:47           ` Greg KH
2019-09-17  6:04           ` Ju Hyung Park
2019-09-17  6:04             ` Ju Hyung Park
2019-09-18  2:35             ` Namjae Jeon
2019-09-18  2:35               ` Namjae Jeon
2019-09-18  6:16               ` 'Greg KH'
2019-09-18  6:16                 ` 'Greg KH'
2019-09-18  6:33                 ` Sergey Senozhatsky
2019-09-18  6:33                   ` Sergey Senozhatsky
2019-09-18  8:26                   ` 'Greg KH'
2019-09-18  8:26                     ` 'Greg KH'
2019-09-18  8:51                     ` Sergey Senozhatsky
2019-09-18  8:51                       ` Sergey Senozhatsky
2019-09-18  9:01                     ` Ju Hyung Park
2019-09-18  9:01                       ` Ju Hyung Park
2019-09-18  9:24                       ` Dan Carpenter
2019-09-18  9:24                         ` Dan Carpenter
2019-09-18  9:53                         ` Ju Hyung Park [this message]
2019-09-18  9:53                           ` Ju Hyung Park
2019-09-18 10:08                           ` Dan Carpenter
2019-09-18 10:08                             ` Dan Carpenter
2019-09-18 10:46                             ` Ju Hyung Park
2019-09-18 10:46                               ` Ju Hyung Park
2019-09-18 11:05                               ` Greg KH
2019-09-18 11:05                                 ` Greg KH
2019-09-19  2:14                         ` Namjae Jeon
2019-09-19  2:14                           ` Namjae Jeon
2019-09-30  4:25                         ` Namjae Jeon
2019-09-30  4:25                           ` Namjae Jeon
2019-09-30  6:08                           ` 'Greg KH'
2019-09-30  6:08                             ` 'Greg KH'
2019-09-17  4:56     ` 'Greg KH'
2019-09-17  4:56       ` 'Greg KH'
2019-09-17  5:15     ` Gao Xiang
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-14 13:39   ` Park Ju Hyung
2019-09-15 13:54   ` Greg KH
2019-09-15 13:54     ` Greg KH
2019-09-15 16:11     ` Ju Hyung Park
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='CAD14+f1yQWoZH4onJwbt1kezxyoHW147HA-1p+U0dVo3r=mqBw@mail.gmail.com' \
    --to=qkrwngud825@gmail.com \
    --cc=alexander.levin@microsoft.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --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=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 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.