From: 'Christoph Hellwig' <hch@infradead.org>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: linux-cifsd-devel@lists.sourceforge.net, linux-cifs@vger.kernel.org
Subject: ksmbd mailing list
Date: Tue, 22 Jun 2021 07:12:10 +0100 [thread overview]
Message-ID: <YNF/OpvdMLbIDZiZ@infradead.org> (raw)
Is there a good reason to have a ksmbd-specific list instead of pooling
all the smb3 knowledge on a single list, similar to how nfs development
works?
next reply other threads:[~2021-06-22 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210622061228epcas1p247d557ef24a971eaf395edd6174bed5e@epcas1p2.samsung.com>
2021-06-22 6:12 ` 'Christoph Hellwig' [this message]
2021-06-22 6:58 ` ksmbd mailing list Namjae Jeon
2021-06-22 10:37 ` Aurélien Aptel
2021-06-23 2:41 ` Namjae Jeon
2021-06-23 2:52 ` Steve French
2021-06-23 4:01 ` Namjae Jeon
2021-06-23 4:52 ` Christoph Hellwig
2021-06-23 5:04 ` 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=YNF/OpvdMLbIDZiZ@infradead.org \
--to=hch@infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=namjae.jeon@samsung.com \
/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.