From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Christoph Hellwig'" <hch@infradead.org>
Cc: <linux-cifsd-devel@lists.sourceforge.net>,
<linux-cifs@vger.kernel.org>,
"'Steve French'" <smfrench@gmail.com>,
"'ronnie sahlberg'" <ronniesahlberg@gmail.com>,
<aurelien.aptel@gmail.com>
Subject: RE: ksmbd mailing list
Date: Tue, 22 Jun 2021 15:58:48 +0900 [thread overview]
Message-ID: <013001d76734$0cf3bee0$26db3ca0$@samsung.com> (raw)
In-Reply-To: <YNF/OpvdMLbIDZiZ@infradead.org>
> 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?
There are users who subscribe only to ksmbd-specific list since ksmbd is out of tree. So we specified
both lists in MAINTAINERS. I do not object to use single list and kill the specific list after
ksmbd is merged into mainline.
Add CC: Steve, Ronnie, Aurélien.
Any opinions?
Thanks!
next prev parent reply other threads:[~2021-06-22 6:58 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 ` ksmbd mailing list 'Christoph Hellwig'
2021-06-22 6:58 ` Namjae Jeon [this message]
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='013001d76734$0cf3bee0$26db3ca0$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=aurelien.aptel@gmail.com \
--cc=hch@infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox