From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: Namjae Jeon <namjae.jeon@samsung.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
smfrench@gmail.com, senozhatsky@chromium.org, hyc.lee@gmail.com,
viro@zeniv.linux.org.uk, hch@lst.de, hch@infradead.org,
ronniesahlberg@gmail.com, aurelien.aptel@gmail.com,
sandeen@sandeen.net, dan.carpenter@oracle.com,
colin.king@canonical.com, rdunlap@infradead.org,
willy@infradead.org
Subject: Re: [PATCH v2 00/10] cifsd: introduce new SMB3 kernel server
Date: Wed, 28 Apr 2021 19:57:02 -0400 [thread overview]
Message-ID: <20210428235702.GE7400@fieldses.org> (raw)
In-Reply-To: <875z06vyi6.fsf@suse.com>
On Thu, Apr 29, 2021 at 12:24:17AM +0200, Aurélien Aptel wrote:
> "J. Bruce Fields" <bfields@fieldses.org> writes:
> > I'd rather see multiple patches that were actually functional at each
> > stage: e.g., start with a server that responds to some sort of rpc-level
> > ping but does nothing else, then add basic file IO, etc.
> >
> > I don't know if that's practical.
>
> Although it would certainly be nice I don't think it's realistic to
> expect this kind of retro-logical-rewriting. AFAIK the other new
> fs-related addition (ntfs patchset) is using the same trick of adding
> the Makefile at the end after it was suggested on the mailing list. So
> there's a precedent.
OK, I wondered if that might be the case.
I don't love it, but, fair enough, maybe that's the best compromise.
--b.
next prev parent reply other threads:[~2021-04-28 23:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210422003835epcas1p246c40c6a6bbc0e9f5d4ccf9b69bef0d7@epcas1p2.samsung.com>
2021-04-22 0:28 ` [PATCH v2 00/10] cifsd: introduce new SMB3 kernel server Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 01/10] cifsd: add document Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 02/10] cifsd: add server handler Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 03/10] cifsd: add trasport layers Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 04/10] cifsd: add authentication Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 05/10] cifsd: add smb3 engine part 1 Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 06/10] cifsd: add smb3 engine part 2 Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 07/10] cifsd: add oplock/lease cache mechanism Namjae Jeon
2021-04-28 20:16 ` J. Bruce Fields
2021-04-29 0:36 ` Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 08/10] cifsd: add file operations Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 09/10] cifsd: add Kconfig and Makefile Namjae Jeon
2021-04-22 0:28 ` [PATCH v2 10/10] MAINTAINERS: add cifsd kernel server Namjae Jeon
2021-04-27 20:53 ` [PATCH v2 00/10] cifsd: introduce new SMB3 " J. Bruce Fields
2021-04-27 21:38 ` Namjae Jeon
2021-04-28 19:13 ` J. Bruce Fields
2021-04-29 0:07 ` Namjae Jeon
2021-04-28 19:18 ` J. Bruce Fields
2021-04-28 20:19 ` Aurélien Aptel
2021-04-28 20:40 ` J. Bruce Fields
2021-04-28 22:24 ` Aurélien Aptel
2021-04-28 23:57 ` J. Bruce Fields [this message]
2021-04-29 0:18 ` 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=20210428235702.GE7400@fieldses.org \
--to=bfields@fieldses.org \
--cc=aaptel@suse.com \
--cc=aurelien.aptel@gmail.com \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=hyc.lee@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=rdunlap@infradead.org \
--cc=ronniesahlberg@gmail.com \
--cc=sandeen@sandeen.net \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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